Hybrid automatic repeat request-acknowledgement (HARQ-ACK) history feedback channel

ABSTRACT

Wireless communications systems and methods related to hybrid automatic repeat request (HARQ) history feedbacks are provided. A user equipment (UE) receives one or more data blocks of a plurality of data blocks, each of the one or more data blocks received in one of a plurality of transmission occasions. The UE transmits an individual feedback for each of the one or more data blocks indicating whether the data block is received successfully. The UE transmits a feedback history report for one or more transmission occasions of the plurality of transmission occasions.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to and the benefit of U.S.Provisional Patent Application No. 62/764,948, filed Aug. 17, 2018, andof U.S. Provisional Patent Application No. 62/717,608, filed Aug. 10,2018, each of which is hereby incorporated by reference in its entiretyas if fully set forth below and for all applicable purposes.

TECHNICAL FIELD

The application technology discussed below relates to wirelesscommunication systems, and more particularly to hybrid automatic repeatrequest (HARQ) history feedbacks. Certain embodiments enable and providesolutions and techniques to improve HARQ communication reliability.

INTRODUCTION

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). A wirelessmultiple-access communications system may include a number of basestations (BSs), each simultaneously supporting communications formultiple communication devices, which may be otherwise known as userequipment (UE).

To meet the growing demands for expanded mobile broadband connectivity,wireless communication technologies are advancing from the long termevolution (LTE) technology to a next generation new radio (NR)technology, which may be referred to as 5^(th) Generation (5G). Forexample, NR is designed to provide a lower latency, a higher bandwidthor a higher throughput, and a higher reliability than LTE. NR isdesigned to operate over a wide array of spectrum bands, for example,from low-frequency bands below about 1 gigahertz (GHz) and mid-frequencybands from about 1 GHz to about 6 GHz, to high-frequency bands such asmillimeter wave (mmWave) bands. NR is also designed to operate acrossdifferent spectrum types, from licensed spectrum to unlicensed andshared spectrum. Spectrum sharing enables operators to opportunisticallyaggregate spectrums to dynamically support high-bandwidth services.Spectrum sharing can extend the benefit of NR technologies to operatingentities that may not have access to a licensed spectrum.

One approach to providing a high-reliability communication is to applyHARQ techniques. For example, a BS may transmit a downlink (DL)transmission to a UE and the UE may provide the BS with a receptionstatus of the DL transmission. If the UE receives the DL transmissionsuccessfully, the UE may transmit a HARQ-acknowledgement (HARQ-ACK) tothe BS. Conversely, if the UE fails to receive the DL transmissionsuccessfully, the UE may transmit a HARQ-negative-acknowledgement(HARQ-NACK) to the BS. Upon receiving a HARQ-NACK from the UE, the BSmay retransmit the DL transmission. The BS may retransmit the DLtransmission until a HARQ-ACK is received from the UE or reaching acertain retransmission limit.

BRIEF SUMMARY OF SOME EXAMPLES

The following summarizes some aspects of the present disclosure toprovide a basic understanding of the discussed technology. This summaryis not an extensive overview of all contemplated features of thedisclosure and is intended neither to identify key or critical elementsof all aspects of the disclosure nor to delineate the scope of any orall aspects of the disclosure. Its sole purpose is to present someconcepts of one or more aspects of the disclosure in summary form as aprelude to the more detailed description that is presented later.

Embodiments of the present disclosure provide mechanisms for improvingHARQ communication reliability. For example, a base station (BS) mayconfigure a user equipment (UE) to provide HARQ feedback historyinformation. The BS may transmit a plurality of DL communications to theUE during a plurality of transmission occasions. The UE may transmit anindividual HARQ acknowledgment/negative acknowledgement (ACK/NACK)feedback for each received DL communication to the BS. Additionally, theUE may transmit HARQ feedback history information associated with one ormore transmission occasions of the plurality of transmission occasionsto the BS to assist the BS in detecting and/or recovering mis-detectedHARQ feedbacks.

For example, in an aspect of the disclosure, a method of wirelesscommunication includes receiving, by the UE, one or more data blocks,each of the one or more data blocks received in one of a pluralitytransmission occasions. The method further includes transmitting, by theUE, an individual feedback for each of the one or more data blocksindicating whether the data block is received successfully. The methodfurther includes transmitting, by the UE, a feedback history report forone or more transmission occasions of the plurality of transmissionoccasions.

In an additional aspect of the disclosure, a method of wirelesscommunication includes transmitting, by a BS to a UE, a plurality ofdata blocks during a plurality of transmission occasions. The methodfurther includes receiving, by the BS from the UE, an individualfeedback for at least a first data block of the plurality of datablocks, the individual feedback indicating whether the first data blockis received successfully. The method further includes receiving, by theBS from the UE, a feedback history report for one or more transmissionoccasions of the plurality of transmission occasions.

In an additional aspect of the disclosure, a UE includes a transceiverconfigured to receive one or more data blocks, each of the one or moredata blocks received in one of a plurality of transmission occasions.The transceiver is further configured to transmit an individual feedbackfor each of the one or more data blocks indicating whether the datablock is received successfully. The transceiver is further configured totransmit a feedback history report for one or more transmissionoccasions of the plurality of transmission occasions.

Other aspects, features, and embodiments of the present invention willbecome apparent to those of ordinary skill in the art, upon reviewingthe following description of specific, exemplary embodiments of thepresent invention in conjunction with the accompanying figures. Whilefeatures of the present invention may be discussed relative to certainembodiments and figures below, all embodiments of the present inventioncan include one or more of the advantageous features discussed herein.In other words, while one or more embodiments may be discussed as havingcertain advantageous features, one or more of such features may also beused in accordance with the various embodiments of the inventiondiscussed herein. In similar fashion, while exemplary embodiments may bediscussed below as device, system, or method embodiments it should beunderstood that such exemplary embodiments can be implemented in variousdevices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network according to someembodiments of the present disclosure.

FIG. 2 is a timing diagram illustrating a transmission frame structureaccording to some embodiments of the present disclosure.

FIG. 3 illustrates a hybrid automatic repeat request (HARQ)communication scenario according to some embodiments of the presentdisclosure.

FIG. 4 illustrates a HARQ processing scenario according to someembodiments of the present disclosure.

FIG. 5 is a block diagram of a user equipment (UE) according to someembodiments of the present disclosure.

FIG. 6 is a block diagram of an exemplary base station (BS) according tosome embodiments of the present disclosure.

FIG. 7 illustrates a HARQ feedback history reporting scheme according tosome embodiments of the present disclosure.

FIG. 8 illustrates a HARQ feedback history reporting scheme according tosome embodiments of the present disclosure.

FIG. 9A illustrates a HARQ feedback history reporting scheme accordingto some embodiments of the present disclosure.

FIG. 9B illustrates a HARQ feedback history reporting scheme accordingto some embodiments of the present disclosure.

FIG. 10 illustrates a HARQ feedback history reporting scheme accordingto some embodiments of the present disclosure.

FIG. 11 illustrates a HARQ feedback history reporting scheme accordingto some embodiments of the present disclosure.

FIG. 12 illustrates a codebook configuration scheme for HARQ feedbacksaccording to some embodiments of the present disclosure.

FIG. 13 is a signaling diagram illustrating a HARQ feedback historyreporting method according to some embodiments of the presentdisclosure.

FIG. 14 is a signaling diagram illustrating a HARQ feedback historyreporting method according to some embodiments of the presentdisclosure.

FIG. 15 is a flow diagram of a communication method according to someembodiments of the present disclosure.

FIG. 16 is a flow diagram of a communication method according to someembodiments of the present disclosure.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to represent the only configurationsin which the concepts described herein may be practiced. The detaileddescription includes specific details for the purpose of providing athorough understanding of the various concepts. However, it will beapparent to those skilled in the art that these concepts may bepracticed without these specific details. In some instances, well-knownstructures and components are shown in block diagram form in order toavoid obscuring such concepts.

This disclosure relates generally to wireless communications systems,also referred to as wireless communications networks. In variousembodiments, the techniques and apparatus may be used for wirelesscommunication networks such as code division multiple access (CDMA)networks, time division multiple access (TDMA) networks, frequencydivision multiple access (FDMA) networks, orthogonal FDMA (OFDMA)networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GlobalSystem for Mobile Communications (GSM) networks, 5^(th) Generation (5G)or new radio (NR) networks, as well as other communications networks. Asdescribed herein, the terms “networks” and “systems” may be usedinterchangeably.

An OFDMA network may implement a radio technology such as evolved UTRA(E-UTRA), Institute of Electrical and Electronics Engineers (IEEE)802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like. UTRA, E-UTRA,and GSM are part of universal mobile telecommunication system (UMTS). Inparticular, long term evolution (LTE) is a release of UMTS that usesE-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documentsprovided from an organization named “3rd Generation Partnership Project”(3GPP), and cdma2000 is described in documents from an organizationnamed “3rd Generation Partnership Project 2” (3GPP2). These variousradio technologies and standards are known or are being developed. Forexample, the 3rd Generation Partnership Project (3GPP) is acollaboration between groups of telecommunications associations thataims to define a globally applicable third generation (3G) mobile phonespecification. 3GPP long term evolution (LTE) is a 3GPP project whichwas aimed at improving the UMTS mobile phone standard. The 3GPP maydefine specifications for the next generation of mobile networks, mobilesystems, and mobile devices. The present disclosure is concerned withthe evolution of wireless technologies from LTE, 4G, 5G, NR, and beyondwith shared access to wireless spectrum between networks using acollection of new and different radio access technologies or radio airinterfaces.

In particular, 5G networks contemplate diverse deployments, diversespectrum, and diverse services and devices that may be implemented usingan OFDM-based unified, air interface. In order to achieve these goals,further enhancements to LTE and LTE-A are considered in addition todevelopment of the new radio technology for 5G NR networks. The 5G NRwill be capable of scaling to provide coverage (1) to a massive Internetof things (IoTs) with a ULtra-high density (e.g., ˜1M nodes/km²),ultra-low complexity (e.g., ˜10s of bits/sec), ultra-low energy (e.g.,˜10+ years of battery life), and deep coverage with the capability toreach challenging locations; (2) including mission-critical control withstrong security to safeguard sensitive personal, financial, orclassified information, ultra-high reliability (e.g., ˜99.999%reliability), ultra-low latency (e.g., ˜1 ms), and users with wideranges of mobility or lack thereof; and (3) with enhanced mobilebroadband including extreme high capacity (e.g., ˜10 Tbps/km²), extremedata rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates),and deep awareness with advanced discovery and optimizations.

The 5G NR may be implemented to use optimized OFDM-based waveforms withscalable numerology and transmission time interval (TTI); having acommon, flexible framework to efficiently multiplex services andfeatures with a dynamic, low-latency time division duplex(TDD)/frequency division duplex (FDD) design; and with advanced wirelesstechnologies, such as massive multiple input, multiple output (MIMO),robust millimeter wave (mmWave) transmissions, advanced channel coding,and device-centric mobility. Scalability of the numerology in 5G NR,with scaling of subcarrier spacing, may efficiently address operatingdiverse services across diverse spectrum and diverse deployments. Forexample, in various outdoor and macro coverage deployments of less than3 GHz FDD/TDD implementations, subcarrier spacing may occur with 15 kHz,for example over 5, 10, 20 MHz, and the like bandwidth (BW). For othervarious outdoor and small cell coverage deployments of TDD greater than3 GHz, subcarrier spacing may occur with 30 kHz over 80/100 MHz BW. Forother various indoor wideband implementations, using a TDD over theunlicensed portion of the 5 GHz band, the subcarrier spacing may occurwith 60 kHz over a 160 MHz BW. Finally, for various deploymentstransmitting with mmWave components at a TDD of 28 GHz, subcarrierspacing may occur with 120 kHz over a 500 MHz BW.

The scalable numerology of the 5G NR facilitates scalable TTI fordiverse latency and quality of service (QoS) requirements. For example,shorter TTI may be used for low latency and high reliability, whilelonger TTI may be used for higher spectral efficiency. The efficientmultiplexing of long and short TTIs to allow transmissions to start onsymbol boundaries. 5G NR also contemplates a self-contained integratedsubframe design with uplink/downlink scheduling information, data, andacknowledgement in the same subframe. The self-contained integratedsubframe supports communications in unlicensed or contention-basedshared spectrum, adaptive uplink/downlink that may be flexiblyconfigured on a per-cell basis to dynamically switch between uplink anddownlink to meet the current traffic needs.

Various other aspects and features of the disclosure are furtherdescribed below. It should be apparent that the teachings herein may beembodied in a wide variety of forms and that any specific structure,function, or both being disclosed herein is merely representative andnot limiting. Based on the teachings herein one of an ordinary level ofskill in the art should appreciate that an aspect disclosed herein maybe implemented independently of any other aspects and that two or moreof these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. For example,a method may be implemented as part of a system, device, apparatus,and/or as instructions stored on a computer readable medium forexecution on a processor or computer. Furthermore, an aspect maycomprise at least one element of a claim.

The present application describes mechanisms for improving HARQcommunication reliability by configuring a UE to provide HARQ feedbackhistory information. For example, a BS may configure the UE with aplurality of transmission occasions. The UE may monitor for DLcommunications from the BS based on the transmission occasions. Uponreceiving a DL communication from the monitoring, the UE transmits anindividual HARQ feedback (e.g., an acknowledgement (ACK) or anegative-acknowledgement (NACK)) for the DL communication. The UE maygenerate a NACK for a transmission occasion when the UE does not receiveany DL communication for the transmission occasion. The UE may recordeach individual feedback for each of the plurality of transmissionoccasion. Additionally, the UE may transmit a HARQ feedback historyreport for one or more transmission occasions of the plurality oftransmission occasions. In some instances, the BS may mis-detect ormisinterpret a HARQ feedback from the UE due to various errors (e.g.,channel errors). The HARQ feedback history report can assist the BS indetecting and/or recovering HARQ ACK/NACK feedback misdetection ormisinterpretation.

In an embodiment, the BS can configure the UE to provide a feedbackhistory report periodically, via a semi-static configuration. In anembodiment, the BS can dynamically trigger the UE to transmit a feedbackhistory report. In an embodiment, the UE is configured to includeindividual HARQ feedbacks for all transmission occasions within areporting period in a feedback history report. In an embodiment, the UEis configured to include individual HARQ feedbacks for a subset of thetransmission occasion within a reporting period in a feedback historyreport. In an embodiment, the BS may request the UE to provide anaggregated decoding result for multiple transmission occasions within areporting period. In an embodiment, the BS may repeat the transmissionof a DL communication over multiple component carriers and/or viamultiple transmission reception points (TRPs) and may request the UE toprovide the feedback history report for a certain component carrierand/or a certain TRP. In an embodiment, the BS may communicate DLcommunications for a plurality of services (e.g., an enhanced mobilebroadband (eMBB) service and a URLLC service) with the UE and mayrequest the UE to provide the feedback history report for a certainservice. In an embodiment, the BS may communicate DL communications ofdifferent HARQ processes with the UE and may request the UE to provide afeedback history report for a certain HARQ process.

Aspects of the present application can provide several benefits. Forexample, the reporting of HARQ feedback history in addition to theindividual HARQ ACK/NACK feedbacks can allow the BS to detect andrecover individual HARQ feedback that were previously misdetected ormisinterpreted by the BS. Accordingly, the present disclosure canimprove HARQ communication reliability. The reporting of HARQ feedbackhistory on a per component carrier basis and/or per TRP basis can assistthe BS in performing outer-loop tracking on a per component carrierbasis and/or per TRP basis. Accordingly, the present disclosure canimprove outer-loop tracking performance. The selective reporting of HARQfeedback history on a service basis can assist the BS in detectingand/or recovering traffic collisions. Accordingly, the presentdisclosure can provide transmission recovery due to collision.

FIG. 1 illustrates a wireless communication network 100 according tosome embodiments of the present disclosure. The network 100 may be a 5Gnetwork. The network 100 includes a number of base stations (BSs) 105(individually labeled as 105 a. 105 b, 105 c, 105 d, 105 e, and 105 f)and other network entities. A BS 105 may be a station that communicateswith UEs 115 and may also be referred to as an evolved node B (eNB), anext generation eNB (gNB), an access point, and the like. Each BS 105may provide communication coverage for a particular geographic area. In3GPP, the term “cell” can refer to this particular geographic coveragearea of a BS 105 and/or a BS subsystem serving the coverage area,depending on the context in which the term is used.

A BS 105 may provide communication coverage for a macro cell or a smallcell, such as a pico cell or a femto cell, and/or other types of cell. Amacro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell, suchas a pico cell, would generally cover a relatively smaller geographicarea and may allow unrestricted access by UEs with service subscriptionswith the network provider. A small cell, such as a femto cell, wouldalso generally cover a relatively small geographic area (e.g., a home)and, in addition to unrestricted access, may also provide restrictedaccess by UEs having an association with the femto cell (e.g., UEs in aclosed subscriber group (CSG), UEs for users in the home, and the like).A BS for a macro cell may be referred to as a macro BS. A BS for a smallcell may be referred to as a small cell BS, a pico BS, a femto BS or ahome BS. In the example shown in FIG. 1, the BSs 105 d and 105 e may beregular macro BSs, while the BSs 105 a-105 c may be macro BSs enabledwith one of three dimension (3D), full dimension (FD), or massive MIMO.The BSs 105 a-105 c may take advantage of their higher dimension MIMOcapabilities to exploit 3D beamforming in both elevation and azimuthbeamforming to increase coverage and capacity. The BS 105 f may be asmall cell BS which may be a home node or portable access point. A BS105 may support one or multiple (e.g., two, three, four, and the like)cells.

The network 100 may support synchronous or asynchronous operation. Forsynchronous operation, the BSs may have similar frame timing, andtransmissions from different BSs may be approximately aligned in time.For asynchronous operation, the BSs may have different frame timing, andtransmissions from different BSs may not be aligned in time.

The UEs 115 are dispersed throughout the wireless network 100, and eachUE 115 may be stationary or mobile. A UE 115 may also be referred to asa terminal, a mobile station, a subscriber unit, a station, or the like.A UE 115 may be a cellular phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, atablet computer, a laptop computer, a cordless phone, a wireless localloop (WLL) station, or the like. In one aspect, a UE 115 may be a devicethat includes a Universal Integrated Circuit Card (UICC). In anotheraspect, a UE may be a device that does not include a UICC. In someaspects, the UEs 115 that do not include UICCs may also be referred toas IoT devices or internet of everything (IoE) devices. The UEs 115a-115 d are examples of mobile smart phone-type devices accessingnetwork 100. A UE 115 may also be a machine specifically configured forconnected communication, including machine type communication (MTC),enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. The UEs 115e-115 k are examples of various machines configured for communicationthat access the network 100. A UE 115 may be able to communicate withany type of the BSs, whether macro BS, small cell, or the like. In FIG.1, a lightning bolt (e.g., communication links) indicates wirelesstransmissions between a UE 115 and a serving BS 105, which is a BSdesignated to serve the UE 115 on the downlink and/or uplink, or desiredtransmission between BSs, and backhaul transmissions between BSs.

In operation, the BSs 105 a-105 c may serve the UEs 115 a and 115 busing 3D beamforming and coordinated spatial techniques, such ascoordinated multipoint (CoMP) or multi-connectivity. The macro BS 105 dmay perform backhaul communications with the BSs 105 a-105 c, as well assmall cell, the BS 105 f. The macro BS 105 d may also transmitsmulticast services which are subscribed to and received by the UEs 115 cand 115 d. Such multicast services may include mobile television orstream video, or may include other services for providing communityinformation, such as weather emergencies or alerts, such as Amber alertsor gray alerts.

The BSs 105 may also communicate with a core network. The core networkmay provide user authentication, access authorization, tracking.Internet Protocol (IP) connectivity, and other access, routing, ormobility functions. At least some of the BSs 105 (e.g., which may be anexample of a gNB or an access node controller (ANC)) may interface withthe core network through backhaul links (e.g., NG-C, NG-U, etc.) and mayperform radio configuration and scheduling for communication with theUEs 115. In various examples, the BSs 105 may communicate, eitherdirectly or indirectly (e.g., through core network), with each otherover backhaul links (e.g., X1, X2, etc.), which may be wired or wirelesscommunication links.

The network 100 may also support mission critical communications withultra-reliable and redundant links for mission critical devices, such asthe UE 115 e, which may be a drone. Redundant communication links withthe UE 115 e may include links from the macro BSs 105 d and 105 e, aswell as links from the small cell BS 105 f. Other machine type devices,such as the UE 115 f (e.g., a thermometer), the UE 115 g (e.g., smartmeter), and UE 115 h (e.g., wearable device) may communicate through thenetwork 100 either directly with BSs, such as the small cell BS 105 f,and the macro BS 105 e, or in multi-hop configurations by communicatingwith another user device which relays its information to the network,such as the UE 115 f communicating temperature measurement informationto the smart meter, the UE 115 g, which is then reported to the networkthrough the small cell BS 105 f. The network 100 may also provideadditional network efficiency through dynamic, low-latency TDD/FDDcommunications, such as in a vehicle-to-vehicle (V2V)

In some implementations, the network 100 utilizes OFDM-based waveformsfor communications. An OFDM-based system may partition the system BWinto multiple (K) orthogonal subcarriers, which are also commonlyreferred to as subcarriers, tones, bins, or the like. Each subcarriermay be modulated with data. In some instances, the subcarrier spacingbetween adjacent subcarriers may be fixed, and the total number ofsubcarriers (K) may be dependent on the system BW. The system BW mayalso be partitioned into subbands. In other instances, the subcarrierspacing and/or the duration of TTIs may be scalable.

In an embodiment the BSs 105 can assign or schedule transmissionresources (e.g., in the form of time-frequency resource blocks (RB)) fordownlink (DL) and uplink (UL) transmissions in the network 100. DLrefers to the transmission direction from a BS 105 to a UE 115, whereasUL refers to the transmission direction from a UE 115 to a BS 105. Thecommunication can be in the form of radio frames. A radio frame may bedivided into a plurality of subframes or slots, for example, about 10.Each slot may be further divided into mini-slots. In a FDD mode,simultaneous UL and DL transmissions may occur in different frequencybands. For example, each subframe includes a UL subframe in a ULfrequency band and a DL subframe in a DL frequency band. In a TDD mode,UL and DL transmissions occur at different time periods using the samefrequency band. For example, a subset of the subframes (e.g., DLsubframes) in a radio frame may be used for DL transmissions and anothersubset of the subframes (e.g., UL subframes) in the radio frame may beused for UL transmissions.

The DL subframes and the UL subframes can be further divided intoseveral regions. For example, each DL or UL subframe may havepre-defined regions for transmissions of reference signals, controlinformation, and data. Reference signals are predetermined signals thatfacilitate the communications between the BSs 105 and the UEs 115. Forexample, a reference signal can have a particular pilot pattern orstructure, where pilot tones may span across an operational BW orfrequency band, each positioned at a pre-defined time and a pre-definedfrequency. For example, a BS 105 may transmit cell specific referencesignals (CRSs) and/or channel state information-reference signals(CSI-RSs) to enable a UE 115 to estimate a DL channel. Similarly, a UE115 may transmit sounding reference signals (SRSs) to enable a BS 105 toestimate a UL channel. Control information may include resourceassignments and protocol controls. Data may include protocol data and/oroperational data. In some embodiments, the BSs 105 and the UEs 115 maycommunicate using self-contained subframes. A self-contained subframemay include a portion for DL communication and a portion for ULcommunication. A self-contained subframe can be DL-centric orUL-centric. A DL-centric subframe may include a longer duration for DLcommunication than for UL communication. A UL-centric subframe mayinclude a longer duration for UL communication than for ULcommunication.

In an embodiment, the network 100 may be an NR network deployed over alicensed spectrum. The BSs 105 can transmit synchronization signals(e.g., including a primary synchronization signal (PSS) and a secondarysynchronization signal (SSS)) in the network 100 to facilitatesynchronization. The BSs 105 can broadcast system information associatedwith the network 100 (e.g., including a master information block (MIB),remaining system information (RMSI), and other system information (OSI))to facilitate initial network access. In some instances, the BSs 105 maybroadcast the PSS, the SSS, and/or the MIB in the form ofsynchronization signal block (SSBs) over a physical broadcast channel(PBCH) and may broadcast the RMSI and/or the OSI over a physicaldownlink shared channel (PDSCH).

In an embodiment, a UE 115 attempting to access the network 100 mayperform an initial cell search by detecting a PSS from a BS 105. The PSSmay enable synchronization of period timing and may indicate a physicallayer identity value. The UE 115 may then receive a SSS. The SSS mayenable radio frame synchronization, and may provide a cell identityvalue, which may be combined with the physical layer identity value toidentify the cell. The PSS and the SSS may be located in a centralportion of a carrier or any suitable frequencies within the carrier.

After receiving the PSS and SSS, the UE 115 may receive a MIB. The MIBmay include system information for initial network access and schedulinginformation for RMSI and/or OSI. After decoding the MIB, the UE 115 mayreceive RMSI and/or OSI. The RMSI and/or OSI may include radio resourcecontrol (RRC) information related to random access channel (RACH)procedures, paging, control resource set (CORESET) for physical downlinkcontrol channel (PDCCH) monitoring, physical uplink control channel(PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.

After obtaining the MIB, the RMSI and/or the OSI, the UE 115 can performa random access procedure to establish a connection with the BS 105. Insome examples, the random access procedure may be a four-step randomaccess procedure. For example, the UE 115 may transmit a random accesspreamble and the BS 105 may respond with a random access response. Therandom access response (RAR) may include a detected random accesspreamble identifier (ID) corresponding to the random access preamble,timing advance (TA) information, a UL grant, a temporary cell-radionetwork temporary identifier (C-RNTI), and/or a backoff indicator. Uponreceiving the random access response, the UE 115 may transmit aconnection request to the BS 105 and the BS 105 may respond with aconnection response. The connection response may indicate a contentionresolution. In some examples, the random access preamble, the RAR, theconnection request, and the connection response can be referred to asmessage 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4(MSG4), respectively. In some examples, the random access procedure maybe a two-step random access procedure, where the UE 115 may transmit arandom access preamble and a connection request in a single transmissionand the BS 105 may respond by transmitting a random access response anda connection response in a single transmission.

After establishing a connection, the UE 115 and the BS 105 can enter anormal operation stage, where operational data may be exchanged. Forexample, the BS 105 may schedule the UE 115 for UL and/or DLcommunications. The BS 105 may transmit UL and/or DL scheduling grantsto the UE 115 via a PDCCH. The BS 105 may transmit a DL communicationsignal to the UE 115 via a PDSCH according to a DL scheduling grant. TheUE 115 may transmit a UL communication signal to the BS 105 via a PUSCHand/or PUCCH according to a UL scheduling grant. In some embodiments,the BS 105 may communicate data with the UE 115 using HARQ to improvecommunication reliability.

In an embodiment, the network 100 may operate over a system BW or acomponent carrier BW. The network 100 may partition the system BW intomultiple BWPs (e.g., portions). A BS 105 may dynamically assign a UE 115to operate over a certain BWP (e.g., a certain portion of the systemBW). The assigned BWP may be referred to as the active BWP. The UE 115may monitor the active BWP for signaling information from the BS 105.The BS 105 may schedule the UE 115 for UL or DL communications in theactive BWP. In some embodiments, a BS 105 may assign a pair of BWPswithin the component carrier to a UE 115 for UL and DL communications.For example, the BWP pair may include one BWP for UL communications andone BWP for DL communications.

In an embodiment, the BS 105 may communicate with a UE 115 using HARQtechniques to improve communication reliability, for example, to providea URLLC service with a reliability requirement of about 1e−6. The BS 105may schedule a UE 115 for a PDSCH communication by transmitting a DLgrant in a PDCCH. The BS 105 may transmit a DL data packet to the UE 115according to the schedule in the PDSCH. If the UE 115 receives the DLdata packet successfully, the UE 115 may transmit a HARQ-ACK to the BS105. Conversely, if the UE 115 fails to receive the DL transmissionsuccessfully, the UE 115 may transmit a HARQ-negative-acknowledgement(HARQ-NACK) to the BS 105. In some examples, the BS 105 may schedule theUE 115 to transmit the HARQ feedback in a PUCCH. In some examples, theBS 105 may schedule the UE 115 to transmit the HARQ feedback in a PUSCH.Upon receiving a HARQ-ACK from the UE 115 for the DL data packet, the BS105 may subsequently transmit a new DL data packet to the UE 115.However, upon receiving a HARQ-NACK from the UE 115 for the DL datapacket, the BS 105 may retransmit the DL data packet to the UE 115.According to embodiments of the disclosure, the UE 115 may additionallyprovide the BS 105 with information associated with a history ofHARQ-ACK feedbacks that were sent to the BS 105 to further facilitateand improve HARQ processing at the BS 105. Mechanisms for providingHARQ-ACK feedback history information are described in greater detailherein.

FIG. 2 is a timing diagram illustrating a transmission frame structure200 according to some embodiments of the present disclosure. Thetransmission frame structure 200 may be employed by BSs such as the BSs105 and UEs such as the UEs 115 in a network such as the network 100 forcommunications. In particular, the BS may communicate with the UE usingtime-frequency resources configured as shown in the transmission framestructure 200. In FIG. 2, the x-axes represent time in some arbitraryunits and the y-axes represent frequency in some arbitrary units. Thetransmission frame structure 200 includes a radio frame 201. Theduration of the radio frame 201 may vary depending on the embodiments.In an example, the radio frame 201 may have a duration of about tenmilliseconds. The radio frame 201 includes M number of slots 202, whereM may be any suitable positive integer. In an example, M may be about10.

Each slot 202 includes a number of subcarriers 204 in frequency and anumber of symbols 206 in time. The number of subcarriers 204 and/or thenumber of symbols 206 in a slot 202 may vary depending on theembodiments, for example, based on the channel bandwidth, the subcarrierspacing (SCS), and/or the CP mode. One subcarrier 204 in frequency andone symbol 206 in time forms one resource element (RE) 210 fortransmission.

A BS (e.g., BS 105 in FIG. 1) may schedule a UE (e.g., UE 115 in FIG. 1)for UL and/or DL communications at a time-granularity of slots 202 ormini-slots 208. Each slot 202 may be time-partitioned into K number ofmini-slots 208. Each mini-slot 208 may include one or more symbols 206.The mini-slots 208 in a slot 202 may have variable lengths. For example,when a slot 202 includes N number of symbols 206, a mini-slot 208 mayhave a length between one symbol 206 and (N−1) symbols 206. In someembodiments, a mini-slot 208 may have a length of about two symbols 206,about four symbols 206, or about seven symbols 206.

FIG. 3 illustrates a HARQ communication scenario 300 according to someembodiments of the present disclosure. The scenario 300 may correspondto a HARQ communication scenario in the network 100. In FIG. 3, thex-axis represents time in some arbitrary units. The scenario 300 isdescribed using a substantially similar transmission frame structure asFIG. 2, and may use the same reference numerals as in FIG. 2 forsimplicity sake.

In the scenario 300, a BS 304 (e.g., the BSs 105) may communicate DLdata with a UE 302 (e.g., the UEs 115) using HARQ. For HARQcommunications, a transmitting node (e.g., the BS 304) may transmit datato a receiving node (e.g., the BS 304). The receiving node may providethe transmitting node with a feedback on the reception status of thedata. For example, the receiving node may transmit an ACK to thetransmitting node to indicate a successful decoding of the data.Conversely, the receiving node may transmit a NACK to the transmittingnode to indicate a decoding failure for the data. When the transmittingnode receives an ACK from the receiving node, the transmitting node maytransmit new data in a subsequent transmission. However, when thetransmitting node receives a NACK from the receiving node, thetransmitting node may retransmit the same data to the receiving node. Inan example, the transmitting node may transmit the same encoding versionof the data in the initial transmission and the retransmission. In anexample, the transmitting node may transmit different encoding versionsof the data in the initial transmission and the retransmission. In anexample, the receiving node may apply soft-combining to combine theencoded data received from the initial transmission and theretransmission for decoding. For simplicity of discussion andillustration, FIG. 3 illustrates the HARQ communication in the contextof DL data communications, though similar HARQ mechanisms may be appliedto UL data communications.

In an example, the BS 304 includes a HARQ component 310. The HARQcomponent 310 is configured to perform multiple parallel HARQ processes312 for DL data communications. The HARQ processes 312 may operateindependent of each other. In other words, the ACKs, NACKs, and/orretransmissions are determined and processed separately for each HARQprocess at the BS 304 and at the UE 302. Each HARQ process 312 may beidentified by a HARQ process ID. For example, the HARQ processes 312 maybe identified by identifiers H1, H2, . . . Hn. The BS 304 maycommunicate with the UE 302 in units of slots 202. The slots 202 areshown as S1, S2, . . . , S8. The BS 304 may configure the UE 302 with aplurality of potential transmission occasions 322 (e.g., PDSCHtransmission occasions) in the slots 202. In other words, the BS 304 maypotentially transmit a DL communication signal to the UE 302 in each ofthe transmission occasions 322. Accordingly, the UE 302 may monitor fora DL transmission from the BS 304 in each transmission occasion 322.

For purposes of simplicity of discussion, FIG. 3 illustrates HARQtransmissions for one HARQ process H1 312, though it will be recognizedthat embodiments of the present disclosure may scale to many more HARQprocesses 312 (e.g., 2, 3, to 16). As shown, the BS 304 transmits ascheduling grant 320 a in the slot S2 202 (e.g., via a PDCCH). Thescheduling grant 320 a may be transmitted as a PDCCH DCI. The schedulinggrant 320 a indicates a schedule for a data block 330 (e.g., PDSCH data)in the slot S2 202. In some examples, the scheduling grant 320 a mayadditionally indicate a resource (e.g., in the slot S3 202) fortransmitting a HARQ feedback for the data block 330. Subsequently, theBS 304 transmits the data block 330 (e.g., via a PDSCH) according to theschedule. The data block 330 may be in the form of a transport block(TB). A TB may include an encoded media access control (MAC) layerpacket data unit (PDU) including information bits. For example, the UE302 receives and decodes the data block 330 successfully. Thus, the UE302 transmits an ACK 340 (marked as A) to the BS 304 in the slot S3 202to indicate a successful decoding of the data block 330.

After receiving the ACK 340, the BS 304 transmits a scheduling grant 320b to schedule the UE 302 for a new data block 332 in the slot S4 202.The scheduling grant 320 b may additionally indicate a resource in theslot S5 202 for transmitting a HARQ feedback for the data block 332. Forexample, the UE 302 receives the data block 332, but fails to decode thedata block 332. Thus, the UE 302 transmits a NACK 342 (marked as N), forexample, in the slot S5 202, to indicate a reception failure of the datablock 332.

Upon receiving the NACK 342, the BS 304 transmits a scheduling grant 320c to schedule the UE 302 for a retransmission of the data block 332 inthe slot S6 202. The BS 304 retransmits the data block 332 in the slotS6 202. The retransmitted data block 332 is shown as 332 b. In someexamples, the retransmitted data block 332 b may be identical to theinitial data block 332. In some examples, the retransmitted data block332 b may carry the same information bits as the initial data block 332,but may include a different encoded version than the initial data block332. The UE 302 fails to detect the scheduling grant 320 c, and thus maynot transmits any ACK or NACK for the data block 332 b (shown by crosssymbol in the slot S7 202). When no ACK or NACK is received for the datablock 332 b, the BS 304 may again retransmit the data block 332. The BS304 may retransmit the data block 332 multiple times until the UE 302receives the data block 332 correctly or when reaching a certainretransmission limit.

As can be observed from the scenario 300, DL communication errors (wherethe UE 302 fails to detect and/or decode a PDCCH or a PDSCH) can becorrected through HARQ retransmission. However, the DL communicationreliability may also rely on UL communication reliability, which may notbe corrected by HARQ as shown in FIG. 4 below.

FIG. 4 illustrates a HARQ processing scenario 400 according to someembodiments of the present disclosure. The scenario 400 may correspondto a HARQ communication scenario in the network 100. The scenario 400illustrates HARQ processing at a UE 402 (e.g., the UEs 115 and/or 302)and at a BS 404 (e.g., the BSs 105 and/or 304). The BS 404 may configurethe UE 402 with transmission occasions (e.g., the transmission occasions322). The UE 402 may monitor for a DL transmission from the BS 404according to the transmission occasions.

The HARQ processing at the BS 404 is shown on the right-side of FIG. 4.At step 440, the BS 404 transmits a PDCCH signal and a PDSCH signal. ThePDCCH signal may carry a scheduling grant (e.g., the scheduling grants320) for the PDSCH signal. The PDSCH signal may carry DL data (e.g., thedata blocks 330 and 332). The BS 404 may monitor for a feedback from theBS 404. At step 445, the BS 404 detects an ACK (e.g., the ACK 340) fromthe UE 402. At step 450, after detecting an ACK, the BS 404 schedules anew PDSCH transmission. Alternatively, at step 455, the BS 404 detects aNACK (e.g., the NACK 342) from the UE 402. At step 460, after detectinga NACK, the BS 404 schedules a retransmission of the PDSCH signal.

The HARQ processing at the UE 402 is shown on the left-side of FIG. 4.At step 410, the UE 402 determines whether a PDCCH (e.g., a schedulinggrant 320) is detected from the BS 404 during a transmission occasion.When no PDCCH is detected, the UE 402 does not transmit any ACK/NACK tothe BS 404 as shown by the step 430 and may be referred to asdiscontinuous transmission (DTX). Otherwise, the UE 402 proceeds to step415. At step 415, the UE 402 receives a PDSCH transmission as scheduledby the PDCCH. At step 420, the UE 402 determines whether the PDSCHtransmission is decoded successfully. When the PDSCH transmission issuccessfully decoded, the UE 402 proceeds to step 425. At step 425, theUE 402 transmits an ACK (e.g., the ACK 340) indicating that the PDSCHtransmission is successfully decoded. When the PDSCH transmission is notsuccessfully decoded, the UE 402 proceeds to step 435. At step 435, theUE 402 transmits a NACK (e.g., the NACK 342) indicating that thedecoding of the PDSCH transmission fails.

Two types of UL error events may occur at the BS 404. The first type ofUL error is a DTX-to-ACK error (shown by the dashed arrow 406), wherethe BS 404 erroneously detects an ACK when the UE 402 did not transmitany ACK/NACK feedback due to an undetected PDCCH error. The second typeof UL error is a NACK to ACK error (shown by the dashed arrow 408),where the UE 402 transmits a NACK, but the BS 404 mis-detects the NACKas an ACK. As can be observed from the scenario 400, when a ULDTX-to-ACK error or a UL NACK-to-ACK occurs, the BS 404 may simplyproceed to a new PDSCH transmission, leaving the UE 402 with a PDSCHerror.

Accordingly, the present disclosure provides techniques for a UE (e.g.,the UEs 115, 302, and/or 402) to provide ACK/NACK history information toa BS (e.g., the BSs 105, 304, and/or 404), for example, via a ACK/NACKhistory feedback channel. The ACK/NACK history may assist the BS todetect and/or recover UL errors, such as DTX-to-ACK errors andNACK-to-ACK errors, that may occur in HARQ communications.

FIG. 5 is a block diagram of an exemplary UE 500 according toembodiments of the present disclosure. The UE 500 may be a UE 115, a UE302, or a UE 402 discussed above in FIGS. 1, 3, 4, respectively. Asshown, the UE 500 may include a processor 502, a memory 504, a HARQmodule 508, a transceiver 510 including a modem subsystem 512 and aradio frequency (RF) unit 514, and one or more antennas 516. Theseelements may be in direct or indirect communication with each other, forexample via one or more buses.

The processor 502 may include a central processing unit (CPU), a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a controller, a field programmable gate array (FPGA) device,another hardware device, a firmware device, or any combination thereofconfigured to perform the operations described herein. The processor 502may also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The memory 504 may include a cache memory (e.g., a cache memory of theprocessor 502), random access memory (RAM), magnetoresistive RAM (MRAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), flash memory, solid state memorydevice, hard disk drives, other forms of volatile and non-volatilememory, or a combination of different types of memory. In an embodiment,the memory 504 includes a non-transitory computer-readable medium. Thememory 504 may store, or have recorded thereon, instructions 506. Theinstructions 506 may include instructions that, when executed by theprocessor 502, cause the processor 502 to perform the operationsdescribed herein with reference to the UEs 115 in connection withembodiments of the present disclosure, for example, aspects of FIGS.7-16. Instructions 506 may also be referred to as program code. Theprogram code may be for causing a wireless communication device toperform these operations, for example by causing one or more processors(such as processor 502) to control or command the wireless communicationdevice to do so. The terms “instructions” and “code” should beinterpreted broadly to include any type of computer-readablestatement(s). For example, the terms “instructions” and “code” may referto one or more programs, routines, sub-routines, functions, procedures,etc. “Instructions” and “code” may include a single computer-readablestatement or many computer-readable statements.

The HARQ module 508 may be implemented via hardware, software, orcombinations thereof. For example, the HARQ module 508 may beimplemented as a processor, circuit, and/or instructions 506 stored inthe memory 504 and executed by the processor 502. In some examples, theHARQ module 508 can be integrated within the modem subsystem 512. Forexample, HARQ module 508 can be implemented by a combination of softwarecomponents (e.g., executed by a DSP or a general processor) and hardwarecomponents (e.g., logic gates and circuitry) within the modem subsystem512.

The HARQ module 508 may be used for various aspects of the presentdisclosure, for example, aspects of FIGS. 7-16. The HARQ module 508 isconfigured to monitor for a plurality of data blocks (e.g., the datablocks 330 and 332) from a BS (e.g., the BSs 105, 304, and/or 404)during a plurality of transmission occasions (e.g., the transmissionoccasions 322), receive one or more data blocks of the plurality of datablocks based on the monitoring, transmit an individual HARQ ACK/NACKfeedback for each received data block, generate a NACK for eachtransmission occasion with no data block detected, generate a record offeedback history including ACK/NACKs for the plurality of transmissionoccasions, and/or transmit a HARQ feedback history report for one ormore transmission occasions of the plurality of transmission occasionsto the BS.

In an embodiment, the HARQ module 508 is configured to receive a HARQfeedback history reporting configuration from the BS and transmit theHARQ feedback history report based on the configuration. Theconfiguration may be a semi-static configuration or a dynamicconfiguration. In an embodiment, the configuration configures the UE 500to include individual HARQ feedbacks for all transmission occasionswithin a reporting period in a feedback history report. In anembodiment, the configuration configures the UE 500 to includeindividual HARQ feedbacks for a subset of the transmission occasionwithin a reporting period in a feedback history report. In anembodiment, the configuration configures the UE 500 to provide anaggregated decoding result for multiple transmission occasions within areporting period. In an embodiment, the BS may repeat the transmissionof a data block over multiple component carriers and/or via multipleTRPs and the configuration request the UE 500 to provide the feedbackhistory report for a certain component carrier and/or a certain TRP. Inan embodiment, the BS may communicate DL communications for a pluralityof services (e.g., an eMBB service and a URLLC service) with the UE 500and the configuration may request the UE 500 to provide the feedbackhistory report for a certain service. In an embodiment, the BS maycommunicate DL communications of different HARQ processes with the UE500 and the configuration configures the UE 500 to provide a feedbackhistory report for a certain HARQ process. Mechanisms for HARQ feedbackhistory reporting are described in greater detail herein.

As shown, the transceiver 510 may include the modem subsystem 512 andthe RF unit 514. The transceiver 510 can be configured to communicatebi-directionally with other devices, such as the BSs 105. The modemsubsystem 512 may be configured to modulate and/or encode the data fromthe memory 504 and/or the HARQ module 508 according to a modulation andcoding scheme (MCS), e.g., a low-density parity check (LDPC) codingscheme, a turbo coding scheme, a convolutional coding scheme, a digitalbeamforming scheme, etc. The RF unit 514 may be configured to process(e.g., perform analog to digital conversion or digital to analogconversion, etc.) modulated/encoded data (e.g., HARQ feedbacks, HARQfeedback history reports) from the modem subsystem 512 (on outboundtransmissions) or of transmissions originating from another source suchas a UE 115 or a BS 105. The RF unit 514 may be further configured toperform analog beamforming in conjunction with the digital beamforming.Although shown as integrated together in transceiver 510, the modemsubsystem 512 and the RF unit 514 may be separate devices that arecoupled together at the UE 115 to enable the UE 115 to communicate withother devices.

The RF unit 514 may provide the modulated and/or processed data, e.g.data packets (or, more generally, data messages that may contain one ormore data packets and other information), to the antennas 516 fortransmission to one or more other devices. The antennas 516 may furtherreceive data messages transmitted from other devices. The antennas 516may provide the received data messages for processing and/ordemodulation at the transceiver 510. The transceiver 510 may provide thedemodulated and decoded data (e.g., DL data blocks, HARQ feedbackhistory configuration) to the HARQ module 508 for processing. Theantennas 516 may include multiple antennas of similar or differentdesigns in order to sustain multiple transmission links. The RF unit 514may configure the antennas 516.

In an example, the transceiver 510 is configured to receive a pluralityof DL communications from a BS, transmit, to the BS, an individual HARQfeedbacks for each received DL communication, receive a HARQ feedbackhistory configuration from the BS, and/or transmit a HARQ feedbackhistory report to the BS based on the configuration, for example, bycoordinating with the HARQ module 508.

In an embodiment, the UE 500 can include multiple transceivers 510implementing different RATs (e.g., NR and LTE). In an embodiment, the UE500 can include a single transceiver 510 implementing multiple RATs(e.g., NR and LTE). In an embodiment, the transceiver 510 can includevarious components, where different combinations of components canimplement different RATs.

FIG. 6 is a block diagram of an exemplary BS 600 according toembodiments of the present disclosure. The BS 600 may be a BS 105, BS304, or BS 404 as discussed above in FIGS. 1, 3, and 4, respectively. Asshown, the BS 600 may include a processor 602, a memory 604, a HARQmodule 608, a transceiver 610 including a modem subsystem 612 and a RFunit 614, and one or more antennas 616. These elements may be in director indirect communication with each other, for example via one or morebuses.

The processor 602 may have various features as a specific-typeprocessor. For example, these may include a CPU, a DSP, an ASIC, acontroller, a FPGA device, another hardware device, a firmware device,or any combination thereof configured to perform the operationsdescribed herein. The processor 602 may also be implemented as acombination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The memory 604 may include a cache memory (e.g., a cache memory of theprocessor 602), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, asolid state memory device, one or more hard disk drives, memristor-basedarrays, other forms of volatile and non-volatile memory, or acombination of different types of memory. In some embodiments, thememory 604 may include a non-transitory computer-readable medium. Thememory 604 may store instructions 606. The instructions 606 may includeinstructions that, when executed by the processor 602, cause theprocessor 602 to perform operations described herein, for example,aspects of FIGS. 76-16. Instructions 606 may also be referred to ascode, which may be interpreted broadly to include any type ofcomputer-readable statement(s) as discussed above with respect to FIG.5.

The HARQ module 608 may be implemented via hardware, software, orcombinations thereof. For example, the HARQ module 608 may beimplemented as a processor, circuit, and/or instructions 606 stored inthe memory 604 and executed by the processor 602. In some examples, theHARQ module 608 can be integrated within the modem subsystem 612. Forexample, HARQ module 608 can be implemented by a combination of softwarecomponents (e.g., executed by a DSP or a general processor) and hardwarecomponents (e.g., logic gates and circuitry) within the modem subsystem612.

The HARQ module 608 may be used for various aspects of the presentdisclosure, for example, aspects of FIGS. 7-16. The HARQ module 608 isconfigured to configure a UE (e.g., the UEs 115, 302, 402, and/or 500)with a plurality of transmission occasions (e.g., the transmissionoccasions 322), transmit a plurality of data blocks (e.g., the datablocks 330 and 332) to the UE during the plurality of transmissionoccasions, receive an individual HARQ ACK/NACK feedback for at least oneof the data blocks, and/or receive a HARQ feedback history report forone or more transmission occasions of the plurality of transmissionoccasions from the UE.

In an embodiment, the HARQ module 608 is configured to transmit a HARQfeedback history reporting configuration to configure the UE for HARQfeedback history report transmission. The configuration may be asemi-static configuration or a dynamic configuration. In an embodiment,the configuration configures the UE to include individual HARQ feedbacksfor all transmission occasions within a reporting period in a feedbackhistory report. In an embodiment, the configuration configures the UE toinclude individual HARQ feedbacks for a subset of the transmissionoccasion within a reporting period in a feedback history report. In anembodiment, the configuration configures the UE to provide an aggregateddecoding result for multiple transmission occasions within a reportingperiod. In an embodiment, the BS 600 may repeat the transmission of adata block over multiple component carriers and/or via multiple TRPs andthe configuration request the UE to provide the feedback history reportfor a certain component carrier and/or a certain TRP. In an embodiment,the BS may communicate DL communications for a plurality of services(e.g., an eMBB service and a URLLC service) with the UE and theconfiguration may request the UE 500 to provide the feedback historyreport for a certain service. In an embodiment, the BS 600 maycommunicate DL communications of different HARQ processes with the UEand the configuration configures the UE to provide a feedback historyreport for a certain HARQ process. Mechanisms for HARQ feedback historyreporting are described in greater detail herein.

As shown, the transceiver 610 may include the modem subsystem 612 andthe RF unit 614. The transceiver 610 can be configured to communicatebi-directionally with other devices, such as the UEs 115, 302, 302,and/or 500 and/or another core network element. The modem subsystem 612may be configured to modulate and/or encode data according to a MCS,e.g., a LDPC coding scheme, a turbo coding scheme, a convolutionalcoding scheme, a digital beamforming scheme, etc. The RF unit 614 may beconfigured to process (e.g., perform analog to digital conversion ordigital to analog conversion, etc.) modulated/encoded data (e.g., amulti-grant scheduling grant) from the modem subsystem 612 (on outboundtransmissions) or of transmissions originating from another source suchas a UE 115, 302, or 500. The RF unit 614 may be further configured toperform analog beamforming in conjunction with the digital beamforming.Although shown as integrated together in transceiver 610, the modemsubsystem 612 and/or the RF unit 614 may be separate devices that arecoupled together at the BS 105 to enable the BS 105 to communicate withother devices.

The RF unit 614 may provide the modulated and/or processed data, e.g.data packets (or, more generally, data messages that may contain one ormore data packets and other information), to the antennas 616 fortransmission to one or more other devices. This may include, forexample, transmission of information to complete attachment to a networkand communication with a camped UE 115, 302, or 500 according toembodiments of the present disclosure. The antennas 616 may furtherreceive data messages transmitted from other devices and provide thereceived data messages for processing and/or demodulation at thetransceiver 610. The transceiver 610 may provide the demodulated anddecoded data (e.g., HARQ feedbacks) to the HARQ module 608 forprocessing. The antennas 616 may include multiple antennas of similar ordifferent designs in order to sustain multiple transmission links.

In an example, the transceiver 610 is configured to transmit a pluralityof DL communications to a UE, receive one or more individual HARQfeedbacks for one or more of the DL communication from the UEs, transmita HARQ feedback history configuration to the UE, and/or receive a HARQfeedback history report from the UE based on the configuration, forexample, by coordinating with the HARQ module 608.

In an embodiment, the BS 600 can include multiple transceivers 610implementing different RATs (e.g., NR and LTE). In an embodiment, the BS600 can include a single transceiver 610 implementing multiple RATs(e.g., NR and LTE). In an embodiment, the transceiver 610 can includevarious components, where different combinations of components canimplement different RATs.

In an embodiment, the BS 600 may operate as a TRP. In an embodiment theBS 600 may perform transmission and/or reception via multiple TRPs(e.g., each including at least a RF unit similar to the RF unit 514 andan antenna similar to the antenna 516). In an example, the multiple TRPsare remote TRPs and the BS 600 is in communication with the multipleTRPs.

FIG. 7 illustrates a HARQ feedback history reporting scheme 700according to some embodiments of the present disclosure. The scheme 700may be employed by a BS such as the BSs 105, 304, 404, and/or 600 and aUE such as the UEs 115, 302, 402, and/or 500 in a network such as thenetwork 100. In particular, the UE may provide the BS with a HARQfeedback history. In FIG. 7, the x-axis represents time in somearbitrary units. The scheme 700 is described using the same DL and ULtransmission scenario as in the scenario 300 shown in FIG. 3, and mayuse the same reference numerals as in FIG. 3 for simplicity sake.Similar to the scenario 300, the UE 302 transmit an individual feedback(e.g., an ACK 340 or a NACK 342) for each received data block (e.g., thedata block 330 and 332). However, the UE 302 additionally provides theBS 304 with a record 710 of HARQ feedback history.

For example, the UE 302 generates a record 710 of HARQ feedback historyover a time period 702 (from time T0 to time T1). The UE 302 stores aHARQ feedback in the record 710 for each potential transmission occasion322, for example, in a memory similar to the memory 504. For example,the UE 302 stores, in the record 710, the ACK 340 for the transmissionoccasion 322 in the slot S2 202. The UE 302 stores, in the record 710,the NACK 342 for the transmission occasion 322 in the slot S4 202.Additionally, the UE 302 generates a NACK (e.g., the NACK 342) for eachtransmission occasion 322 that the UE 302 fails to receive acorresponding scheduling grant 320 (e.g., PDCCH) and stores the NACK inthe record 710 for the corresponding transmission occasion 322. In otherwords, the UE 302 may feedback a NACK when no PDCCH is detected or whena NACK is actually transmitted. The UE 302 may store the feedbacks inthe record 710 according to a time order of the transmission occasions322. In other words, the record 710 includes an accumulation of UE 702'sdecoding results for the transmission occasions 322. The following showsan example of the record 710:HARQ feedback history record 710=[N,N,A,N,N,N,N,N],where N represents a NACK 342 and A represents an ACK 340.

The BS 304 may request the UE 302 to transmit a HARQ feedback historyreport 740. The UE may transmit a HARQ feedback history report 740including the record 710, for example, in the slot S8 202. The HARQfeedback history record 710 can assist the BS 304 in detecting ULcommunication errors, such as the DTX-to-ACK error and the NACK-to-ACKerror, described above with respect to FIG. 4. For example, the BS 304may have mis-detected the DTX (e.g., no feedback transmission) in theslot S7 202 as an ACK or the NACK 342 in the slot S5 202 as an ACKduring the earlier UL transmissions. After receiving the HARQ feedbackhistory record 710, the BS 304 may detect the UL error based on acomparison of the earlier UL transmission against the HARQ feedbackhistory record 710. Thus, the BS 304 may retransmit the data block 332to the UE 302 at a later transmission occasion 322.

In an example, the BS 304 may perform inner-loop tracking based on theindividual ACK/NACK feedbacks. The inner-loop tracking may include ULand/or DL power adjustments, DL adaptation of the DL control channel(e.g., PDCCH), DL adaptation of the DL data channel (e.g., PDSCH),and/or any adjustments for UL and/or DL communications. Additionally,the BS 304 may perform outer-loop tracking based on the HARQ feedbackhistory record 710. The outer-loop tracking may include UL and/or DLpower adjustments, DL adaptation of the DL control channel (e.g.,PDCCH). DL adaptation of the DL data channel (e.g., PDSCH), and/or anyadjustments for UL and/or DL communications.

In an example, the BS 304 may configure the UE 302 to provide periodicHARQ feedback history records 710. In an example, the BS 304 mayconfigure the UE 302 to use one codebook for the individual HARQACK/NACK transmission (e.g., the ACKs 340 and the NACKs 342) and anothercodebook for the HARQ feedback history transmission (e.g., the record710). In an example, the BS 304 may configure the UE 302 with certain ULresources (e.g., time-frequency resources) as a HARQ feedback historychannel 704 for HARQ feedback history transmission. In the example shownin FIG. 7, the UL resources for the HARQ feedback history channel 704 islocated in the slot S8 202. The BS 304 may use various mechanisms toconfigure the UE 302 for HARQ feedback history reporting. In an example,the HARQ feedback history configuration may be a semi-static periodicconfiguration via an RRC configuration. In an example, the HARQ feedbackhistory configuration may be a dynamic configuration via a DL controlinformation (DCI) trigger. Mechanisms for HARQ feedback historyconfiguration are described in greater detail herein below.

To improve communication reliability, a network (e.g., the network 100)or a BS (e.g., the BSs 105, 304, 404, and 600) may repeat thetransmission of a data block (e.g., the data blocks 330 and 332) intime, frequency, and/or space. In an example, multiple PDSCH signalscarrying the same data block can be transmitted in different slots(e.g., the slots 202) for the same frequency carrier and the same TRP toachieve power accumulation across time. In an example, multiple PDSCHsignals carrying the same data block can be transmitted in differentcomponent carriers to achieve frequency-diversity. In an example,multiple PDSCH signals carrying the same data block can be transmittedby different TRPs to achieve spatial-diversity.

In a single PDSCH transmission with no repetition, the BS may track thedecoding result of each PDSCH transmission and a corresponding PDCCH DCItransmission based on feedbacks from the UE. For PDCCH, the BS maydetermine the PDDCH decoding result based on whether a correspondingACK/NACK is received from the UE with the exception that the BS may notbe able to distinguish between a DTX and an actual NACK. For PDSCH, theBS may determine PDSCH decoding result based on ACK/NACK feedbacks. Thestatistics of the decoding results may assist the BS to performouter-loop control, for example, DL power adjustments. DL adaptation,and/or determine the quality or performance of the inner-loop control.

To further improve communication reliability, a TB may be transmittedwith repetitions over multiple component carriers. Alternatively orAdditionally, the repetitions can be transmitted from multiple TRPs. Intraditional HARQ processing, when a TB is transmitted with repetitions,the UE may feedback the overall decoding result of the transmissions inthe multiple component carriers and/or from the multiple TRPs, but maynot provide an individual feedback for each copy of the repetition(e.g., each transmission on each component carrier and/or eachtransmission from each TRP). In other words, the UE may provide a singlefeedback per TB. A per TB feedback may be sufficient for data decoding(e.g., HARQ inner-loop control), but may not be sufficient for thepurpose of outer-loop monitoring and/or tracking on a per componentcarrier and/or a per TRP basis.

FIGS. 8, 9A, and 9B illustrate various mechanisms for a UE (e.g., theUEs 115, 302, 402, and/or 500) to report HARQ feedback history toimprove outer-loop performance. In FIGS. 8, 9A, and 9B, the schemes 800and 900 may be employed by a BS such as the BSs 105, 304, 404, and/or600 and a UE such as the UEs 115, 302, 402, and/or 500 in a network suchas the network 100. In particular, the BS may schedule the UE withmultiple PDSCH transmission in different component carriers and/or fromdifferent TRPs. Additionally, FIGS. 8, 9A, and 9B are described usingthe same transmission frame structure as FIG. 2, and may use the samereference numerals as in FIG. 2 for simplicity sake.

FIG. 8 illustrates a HARQ feedback history reporting scheme 800according to some embodiments of the present disclosure. In FIG. 8, thex-axis represents time in some arbitrary units and the y-axis representsfrequency in some arbitrary units. The scheme 800 may use substantiallysimilar mechanism for HARQ communications as in the schemes 300 and 700,but may use multiple component carriers for communications to obtainfrequency-diversity. FIG. 8 illustrates DL communications transmittedover two component carriers, a component carrier C1 C1 806 and acomponent carrier C2 C2 808 for purposes of simplicity of discussion,though it will be recognized that embodiments of the present disclosuremay scale to many more component carriers (e.g., 3, 4, or more).

In the scheme 800, a BS 804 (e.g., the BSs 105, 304, 404, and/or 600)transmits a plurality of DL communications 810 to a UE 802 (e.g., theUEs 115, 302, 402, and/or 500). The BS 804 transmits each DLcommunication 810 in the component carrier C1 806 and the componentcarrier C2 808. Each DL communication 810 may correspond to a TB similarto the data blocks 330 and 332. The TB may include DL data associatedwith a certain HARQ process similar to the HARQ processes 312. Thetransmissions on the component carriers C1 806 and C2 808 are repetitivetransmissions of the TB or DL data. As shown by the reference numeral852, the transmission on the component carrier C1 806 is referred to as810 a, and the transmission on the component carrier C2 808 is referredto as 810 b. Further, the BS 804 can schedule the DL communication 810 aand the DL communication 810 b to be transmitted at the same time duringa slot k 202. Each DL communication 810 a, 810 b may be transmitted viaa PDSCH channel. The BS 804 may transmit a first DL communication 810(including a DL communication 810 a on the component carrier C1 806 anda DL communication 810 b on the component carrier C2 808), a second DLcommunication 810 (including a DL communication 810 a on the componentcarrier C1 806 and a DL communication 810 b on the component carrier C2808), and so on.

In an example, the BS 804 may configure the UE 802 with a plurality oftransmission occasions (e.g., the transmission occasions 322) for thecomponent carrier C1 806 and a plurality of transmission occasions forthe component carrier C2 808. For each DL communication 810 on eachcomponent carrier C1 806 and component carrier C2 808, the BS 804 mayprovide the UE 802 with a corresponding DL scheduling grant (e.g., thescheduling grants 320). The UE 802 may monitor for a scheduling grantfrom the BS 804 in the component carrier C1 806 and component carrier C2808 based on the configured transmission occasions. The UE 802 mayreceive DL communications from the BS 804 based on detected schedulinggrant.

The UE 802 may receive a first DL communication 810 (including a DLcommunication 810 a on the component carrier C1 806 and a DLcommunication 810 b on the component carrier C2 808), a second DLcommunication 810 (including a DL communication 810 a on the componentcarrier C1 806 and a DL communication 810 b on the component carrier C2808), and so on. The UE 802 may determine a decoding result 820 for eachreceived DL communication 810 a and each received DL communication 810b. In an example, the UE 802 may transmit an individual feedback foreach received DL communication 810 a and each received DL communication810 b based on corresponding decoding results 820. The UE 802 maytransmit an ACK (e.g., the ACK 340) for a successful decoding andtransmit a NACK (e.g., the NACK 342) for a failed decoding.

In an example, the UE 802 may determine an overall decoding result foreach DL communication 810 (e.g., a TB) based on decoding results 820 forcorresponding the DL communication 810 a and 810 b. For example, the UE802 may determine a success for an overall decoding when the UE 802 cansuccessfully decode any of the repetitions (e.g., the DL communication810 a and 810 b).

Additionally, the UE 802 may record an accumulation of all the decodingresults 820, for example, in a memory similar to the memory 504. Forexample, the UE 802 may generate a record of the decoding, including ineach entry, a decoding result 820 for a DL communication 810 a on thecomponent carrier C1 806, a decoding result 820 for a corresponding DLcommunication 810 b on the component carrier C2 808, and an overalldecoding result 820 for the DL communications 810 a and 810 b.

As shown by the reference numeral 850, for a first DL communication 810,the UE 802 receives a DL communication 810 a from C1 with a successfuldecoding and a DL communication 810 b from C2 with a successfuldecoding. Accordingly, the UE 802 may determine that an overall decodingfor the first DL communication 810 is successful. For a second DLcommunication 810, the UE 802 receives a DL communication 810 a from C1with a successful decoding and a DL communication 810 b from C2 with afailed decoding. Since DL communication 810 a is received successfullyfor the second DL communication 810, the UE 802 may determine that anoverall decoding for the second communication is successful. The UE 802may determine the decoding results for each component carrier C1 806 andC2 808 and an overall decoding for each remaining DL communication 810in a similar manner.

The BS 804 may configure the UE 802 to provide a HARQ feedback historyreport via a HARQ feedback history channel using similar mechanisms asin the scheme 700. To reduce communication overhead, the UE 802 may notrepeat each of the individual feedback or decoding result 820 in thereport. Instead, the UE 802 may compute an aggregated decoding result830 for the DL communications 810 in the record. The UE 802 computes theaggregated decoding result 830 based on the decoding results 820 for thecomponent carrier C1 806 and the component carrier C2 808. The UE 802transmits a HARQ feedback history report 840 including the aggregateddecoding result 830.

The UE 802 may determine an aggregated decoding result 830 based on asuccess rate for the decoding. The success rate can be computed bycounting the number of ACKs for a certain component carrier in thedecoding results 820, counting the number of NACKs for the componentcarrier in the decoding results 820, and determining a ratio between thenumber of ACKs and a total number of ACKs and NACKs for a certaincomponent carrier as shown below:Success rate=Number of ACKs/(Number of ACKs+Number of NACKs).  (1)In an example, the UE 802 determines a success rate on a per componentcarrier basis. For example, the UE 802 determines a decoding successrate of about 71% (e.g., 5/7 Yes) for the component carrier C1 806 and adecoding success rate of about 71% (e.g., 5/7 Yes) for the componentcarrier C2 808. The UE 802 may transmit one HARQ feedback history report840 including the decoding success rate for the component carrier C1 806and the decoding success rate for the component carrier C2 808.Alternatively, the UE 802 may transmit the decoding success rate for thecomponent carrier C1 806 and the decoding success rate C2 808 for thecomponent carrier C2 808 in separate reports 840. In an example, the UE802 determines a success rate for all component carriers based on theoverall decoding results 820. For example, the UE 802 determines anoverall success rate of about 86% (e.g., 6/7 Yes) for the componentcarrier C1 806 and the component carrier C2 808.

In some examples, the BS 804 may configure the UE 802 with a HARQfeedback history report period (e.g., the period 702) and the number ofDL communications 810 to include in a HARQ feedback history report 840may be based on the configured report period. The reporting can be at alow-duty cycle (e.g., at about every 5 ms, 10 ms, 15 ms, or 20 ms ormore). Additionally, the BS 804 may configure the UE 802 to provide anoverall HARQ feedback history report for all component carriers.Alternatively, the BS 804 may configure the UE 802 to provide a HARQfeedback history report on a per component carrier basis. Mechanisms forHARQ feedback history report configuration are described in greaterdetail herein below.

In some examples, the UE 802 may feedback a decoding statistic, forexample, a filtered or averaged decoding result for the HARQ feedbackhistory report period. In some examples, the UE 802 may feedback thefraction of corrected decoded DL communications within a report period.In some examples, the UE 802 may feedback the number of correcteddecoded DL communications within a report period.

In some examples, the HARQ feedback history report 840 may includevarious forms of information associated with the accumulated decodingresults 820 (e.g., including an individual ACK/NACK feedback for eachcommunication 810 a, 810 b and/or the aggregated decoding results 830,such as decoding statistics of the respective decoding results, decodingstatistics of the accumulated decoding results 820 and/or aggregateddecoding results 830, and/or the like. For example, the report 840 mayinclude information identifying a percentage of the plurality ofcommunications, transmitted on the physical DL channel, that weresuccessfully decoded by UE 802. The report 840 may include informationidentifying a ratio of the quantity of the plurality of communications810, transmitted on the physical DL channel, that were successfullydecoded by UE 802 to the quantity of the plurality of communications 810received on the physical DL channel. The report 840 may includeinformation identifying a fraction of the plurality of communications810, transmitted on the physical DL channel, that were successfullydecoded by UE 802. The report 840 may include information identifying aquantity of the plurality of communications 810, transmitted on thephysical DL channel, that were successfully decoded by UE 802. Thereport 840 may include information identifying the particularcommunications, of the plurality of communications 810, transmitted onthe physical DL channel, that were successfully decoded by UE 802. Thereport 840 may include information identifying the particularcommunications, of the plurality of communications 810, transmitted onthe physical DL channel, that were not successfully decoded by UE 802,and/or the like.

In some examples, the report 840 may include one or more bits, flags,values, information fields, and/or the like, representing the decodingstatistics of the respective decoding results, representing the decodingstatistics of the accumulated decoding results 820 and/or aggregateddecoding results 830, and/or the like. For example, the report 840 mayinclude may include a bit that represents a binary indicator of whetherthe percentage of the plurality of communications 810, transmitted onthe physical DL channel, that were successfully decoded by UE 802satisfies or does not satisfy a threshold percentage (e.g., a bit value1 may indicate that the percentage is greater than or equal to 90%, abit value of 0 may indicate that the percentage is less than 90%, and/orthe like). As another example, the report 840 may include two or morebits that represent a percentage range, of a plurality of percentageranges, in which a percentage of the plurality of communications 810,transmitted on the physical DL channel, that were successfully decodedis included. For example, the report 840 may include two bits that mayrepresent a first percentage range, a second percentage range, a thirdpercentage range, and a fourth percentage range. In some examples, theplurality of percentage ranges may be uniform and/or equal (e.g., afirst percentage range r₁ may be 0%≤r₁>25%, the second percentage ranger₂ may be 25%≤r₂>50%, the third percentage range r₃ may be 50%≤r₃>75%,and the fourth percentage range r₄ may be 75%≤r₄>100%), the plurality ofranges may be non-uniform (e.g., where one or more percentage ranges, ofthe plurality of percentage ranges, are larger or smaller than one ormore other percentage ranges of the plurality of percentage ranges,and/or the like). In some examples, the threshold percentage may bedetermined based at least in part on a configuration by the BS 804 viaan RRC configuration, a MAC control element (CE) configuration, or a DCImessage.

In some examples, the report 840 may further include informationidentifying an overall decoding result for each communication (e.g., theDL communication 810 a and 810 b), of the plurality of communications810, that were transmitted on a plurality of physical DL channels inwhich the physical DL channel is included.

In some examples, the BS 804 may request a quantized feedback for thereport 840. For example, the BS 804 may request the UE 802 to partitionthe individual HARQ ACKs/NACKs within a reporting period in the groups,bundle the individual HARQ ACKs/NACKs within one group, and feedback thebundled result (e.g., a single bit indication) for each group.

In some examples, BS 804 may receive the report 840 and may use theinformation associated with the accumulated decoding results 820 and/orthe aggregated decoding results 830 to improve outer-loop control and/ortracking, which may include performing power adjustments for theplurality of physical DL channels, inner-loop control adjustments forthe plurality of physical DL channels, downlink link adaptation for theplurality of physical DL channels, and/or the like.

FIGS. 9A and 9B collectively illustrate a HARQ feedback historyreporting scheme 900 according to some embodiments of the presentdisclosure. In FIG. 9B, the x-axis represents time in some arbitraryunits. The scheme 900 may use substantially similar mechanisms for HARQcommunications as in the schemes 700 and 800, but may use multiple BSsto repeat the transmission of a DL communication. FIGS. 9A and 9Billustrate DL communications 910 a, 910 b, and 910 c transmitted bythree BSs 904 a, 904 b, and 904 c, respectively, for purposes ofsimplicity of discussion, though it will be recognized that embodimentsof the present disclosure may scale to any suitable number of BSs 904(e.g., 2, 4, 5 or more). The BSs 904 may be substantially similar to theBSs 105, 304, 404, 600, and/or 804. While the BSs 904 a, 904 b, and 904c are shown as individual BSs, in some embodiments, the BSs 904 a, 904b, and 904 c may be TRPs associated with a BS (e.g., the BSs 105, 304,404, 600, and 804). In some examples, the TRPs can be co-located withthe BS. In some examples, the TRPs can be located remotely from the BS.

In the scheme 900, for each DL communication 910, the BS 904 a maytransmit a first repetitive transmission 910 a (e.g., via a first PDSCH)to a UE 902 (e.g., the UEs 115, 302, 402, 500, and/or 802), the BS 904 bmay transmit a second repetitive transmission 910 b (e.g., via a secondPDSCH) to the UE 902, the BS 904 c may transmit a third repetitivetransmission 910 c (e.g., via a third PDSCH) to the UE 902. The BSs 904a, 904 b, and 904 c may perform similar transmission for a secondcommunication 910, a third communication 910, and so on. Each DLcommunication 810 may correspond to a TB similar to the data blocks 330and 332. The TB may include DL data associated with a certain HARQprocess similar to the HARQ processes 312. The transmissions from theBSs 904 a, 904 b, and 904 c are repetitive transmissions of the TB or DLdata.

As shown in FIG. 9B, the BS 904 a, BS 904 b, and BS 904 c may transmit aplurality of DL communications 910 across a plurality of slots 202. Fora first DL communication 910, the BS 904 a, BS 904 b, and BS 904 c maytransmit the repetitive transmissions 910 a, 910 b, and 910 c,respectively, in a slot S1 202. For a second DL communication 910, theBS 904 a, BS 904 b, and BS 904 c may transmit the repetitivetransmissions 910 a, 910 b, and 910 c, respectively, in a slot S3 202.For a third DL communication 910, the BS 904 a, BS 904 b, and BS 904 cmay transmit the repetitive transmissions 910 a, 910 b, and 910 c,respectively, in a slot S5 202. For each DL communication 910 a, 910 b,and 910 c, the UE 902 may be configured with a corresponding DLscheduling grant (e.g., the scheduling grants 320). In some examples,the BSs 904 a, 904 b, and 904 c may coordinate with each other for thetransmissions of a particular TB.

In an example, the BS 904 a, 904 b, and/or 904 c may configure the UE802 with a plurality of transmission occasions (e.g., the transmissionoccasions 322). For each DL communication 910 a, 910 b, 910 c, the BS804 may provide the UE 802 with a corresponding DL scheduling grant(e.g., the scheduling grants 320). The UE 902 may monitor for ascheduling grant from the BSs 904 a, 904 b, and/or 904 c based on theconfigured transmission occasions. The UE 902 may receive DLcommunications from the BS 804 based on detected scheduling grant.

The UE 902 may receive a first DL communication 910 (including a DLcommunication 910 a from the BS 904 a, a DL communication 910 b from theBS 904 b, and a DL communication 910 c from the BS 904 c), a second DLcommunication 810 (including a DL communication 910 a from the BS 904 a,a DL communication 910 b from the BS 904 b, and a DL communication 910 cfrom the BS 904 c), and so on. The UE 902 may determine a decodingresult 920 for each received DL communication 910 a, 910 b, and 910 c.In an example, the UE 902 may transmit an individual feedback for eachreceived DL communication 910 a, 910 b, 910 c based on a correspondingdecoding result 920. For example, the UE 902 transmit an ACK (e.g., theACK 340) for a successful decoding and a NACK (e.g., the NACK 342) for afailed decoding.

In an example, the UE 902 may determine an overall decoding result foreach DL communication 910 (e.g., a TB) based on decoding results 920 forcorresponding the DL communications 910 a, 910 b, and 910 c. The UE 902may determine a success for an overall decoding when the UE 902 cansuccessfully decode any of the repetitive transmissions (e.g., the DLcommunication 910 a, 910 b, and 910 c). For example, after receivingeach DL communication 910 (e.g., including the repetitive transmission910 a, 910 b, and 910 c), the UE 902 may transmit a feedback 950including a corresponding overall decoding result 920. As shown in FIG.9B, the UE 902 transmits a feedback 950 for the first DL communication910 in the slot S2 202, transmits a feedback 950 for the second DLcommunication 910 in the slot S4 202, and transmits a feedback 950 forthe third DL communication 910 in the slot S6 202. The UE 902 maytransmit a report 950 for a corresponding DL communication 910 to one ormore of the BSs 904 a, 904 b, and 904 c.

Additionally, the UE 902 may record all the decoding results 920, forexample, in a memory similar to the memory 504. For example, the UE 902may generate a record of the decoding history including in each entry, adecoding result 920 for a DL communication 910 a received from the BS904 a, a decoding result 920 for a DL communication 910 b received fromthe BS 904 b, a decoding result 920 for a DL communication 910 creceived from the BS 904 c, and an overall decoding result 920 for theDL communications 910 a, 910 b, and 910 c. The UE 902 may generatesimilar entries in the record in a similar manner as in the scheme 800,but with decoding results for different BSs 904 instead of for differentcomponent carriers as in the scheme 800.

As shown by the reference numeral 952, for a first DL communication 910,the UE 902 receives a DL communication 910 a from the BS 904 a with asuccessful decoding, a DL communication 910 b from the BS 904 b with asuccessful decoding, and a DL communication 910 c from the BS 904 c witha successful decoding, and thus the UE 902 may determine that an overalldecoding for the first communication is successful. For a secondcommunication, the UE 902 receives a DL communication 910 a from the BS904 a with a failed decoding, a DL communication 910 b from the BS 904 bwith a failed decoding, and a DL communication 910 c from the BS 904 cwith a successful decoding, and thus the UE 902 may determine that anoverall decoding for the second communication is successful. For a thirdcommunication, the UE 902 receives a DL communication 910 a from the BS904 a with a failed decoding, a DL communication 910 b from the BS 904 bwith a successful decoding, and a DL communication 910 c from the BS 904c with a successful decoding, and thus the UE 902 may determine that anoverall decoding for the third communication is successful. Thus, the UE902 may indicate a decoding success for each of the report 950 shown inFIG. 9B.

The BS 904 a, 904 b, and/or 904 c may configure the UE 902 to provide aHARQ feedback history report 940 via a HARQ feedback history channel ina similar manner as in the schemes 700 and 800. The UE 902 may includean accumulation of the decoding results 920 and/or an aggregateddecoding result 930 in the report 940. The UE 902 may use similarmechanisms as described in the scheme 800 to determine the aggregatedresult 930. In the example, the UE 902 determines a decoding successmetric (e.g., represented as a ratio of number of successful decoding tototal number of decoding) for the aggregated decoding results 930 on aper TRP or BS basis. For example, the UE 902 may determine a decodingsuccess metric of 1/3 for the BS 904 a, a decoding success metric of 2/3for the BS 904 b, and a decoding success metric of 3/3 for the BS 904 cbased on corresponding individual decoding results 920. The UE 902 mayfurther determine an aggregated decoding result 930 of 3/3 for theoverall decoding results 920.

The UE 902 transmits a HARQ feedback history report 940 a to the BS 904a, transmit a HARQ feedback history report 940 b to the BS 904 b, andtransmit a HARQ feedback history report 940 c to the BS 904 c. The UE902 may transmit the reports 940 a, 940 b, and 940 c in the slot S7 202as shown in FIG. 9B. Alternatively, the UE 902 may transmit the reports940 a, 940 b, and 940 c in different slots 202. In an example, thereport 940 a may include the aggregated decoding result 930 (e.g., 1/3)for the BS 904 a, the report 940 b may include the aggregated decodingresult 930 (e.g., 2/3) for the BS 904 b, and the report 940 c mayinclude the aggregated decoding result 930 (e.g., 3/3) for the BS 904 c.

In some examples, the UE 902 may configure a HARQ feedback historyreport (e.g., the report 940 a, 940 b, or 940 c) to be transmitted tothe BSs 904 a, 904 b, and 904 c based at least in part on a transmissionconfiguration indicator (TCI) state associated with the BSs 904 a, 904b, and 904 c, based at least in part on a TCI state group associatedwith the BSs 904 a, 904 b, and 904 c, and/or the like. For example, UE902 may transmit the HARQ feedback history on a per TCI state basis, ona per TCI state group basis, and/or the like. As another example, UE 902may include the HARQ feedback history report, for a particular TCI stateand BS (e.g., the BS 904 a, 904 b, or 904 c) combination in a CSI reportassociated with the particular TCI state and BS combination. As afurther example, UE 902 may transmit the HARQ feedback history report ina CSI report associated with a particular TCI group. In some examples,UE 902 may periodically transmit the HARQ feedback history report to theplurality of BSs 904 a, 904 b, and 904 c at a particular time interval(e.g., the time period 702). For example, UE 902 may transmit the HARQfeedback history report to the BSs 904 a, 904 b, and 904 c at the sametime interval. As another example, UE 902 may transmit the HARQ feedbackhistory report to some BSs of the BSs 904 a, 904 b, and 904 c atdifferent time intervals. As a further example, UE 902 may transmit theHARQ feedback history report to each BS of the BSs 904 a, 904 b, and 904c at different time intervals.

In some examples, UE 902 may transmit the HARQ feedback history report940 to the plurality of BSs 904 a, 904 b, and 904 c in a manner similarto that described above in FIG. 8.

In some examples, the information associated with the accumulateddecoding results 920 and/or aggregated decoding results 930, included inthe HARQ feedback history report 940 may include information similar tothat described above in FIG. 8.

In some examples, the plurality of BSs 904 a, 904 b, and 904 c mayreceive the HARQ feedback history report 940 and may use the informationassociated with the accumulated decoding results 920 and/or aggregateddecoding results 930 to jointly and/or individually improve outer-loopcontrol and/or tracking, which may include performing power adjustmentsfor the plurality of physical DL channels, inner-loop controladjustments for the plurality of physical DL channels, downlink linkadaptation for the plurality of physical DL channels, and/or the like.

In some examples, a network (e.g., the network 100) may configure PDSCHrepetitions over multiple component carriers (e.g., the componentcarriers C1 806 and C2 808 a) and/or multiple TRPs (e.g., the BSs 904 a,904 b, 904 c), a UE (e.g., the UEs 115, 302, 402, 500, 802, and/or 902)may feedback one bit for each PDSCH the UE received. In a first option,the UE may feedback per TB ACK/NACK and per PDSCH ACK/NACK. In a secondoption, the UE may feedback per PDSCH ACK/NACK without per TB ACK/NACK.Referring to the example in FIG. 8, the per PDSCH ACK/NACK may refer tothe decoding result 820 for each DL communication 810 a on the componentcarrier C1 806 and each DL communication 810 b on the component carrierC2 808, and the per TB ACK/NACK may refer to the overall decoding result820 each DL communication 810. Referring to the example in FIG. 9, theper PDSCH ACK/NACK may refer to the decoding result 920 for each DLcommunication (e.g., the DL communication 910 a, 910 b, 910 c) from eachBS (e.g., the BS 904 a, 904 b, or 904 c) for each DL communication 910and the per TB ACK/NACK may refer to the overall decoding result 920each DL communication 910. The selection of the first option or thesecond option may depend on whether the UE performs log-likelihood ratio(LLR) soft-combining across repetitions or based on the RRCconfiguration and/or the UE capability. Further, the first option mayrestrict all ACK/NACK bits (for the per TB ACK/NACK and per PDSCHACK/NACK) to be transmitted on a single PUCCH transmission.Alternatively, the network may configure the per TB ACK/NACK to bemultiplexed with one of the PDSCH ACK/NACKs.

In some embodiments, a network (e.g., the network 100) may employ theschemes 800 and 900 in combination to repeat the transmission of a HARQTB over multiple component carriers with different TRPs transmittingover the different component carriers. In such embodiments, the networkmay configure a UE (e.g., the UEs 115, 302, 402, 500, 802, and/or 902)to provide HARQ feedback history report (e.g., the reports 840 and 940)using similar mechanism as in the schemes 800 and 900. For example, thenetwork may configure the UE to report an accumulation of all decodingresults 920 (e.g., including an ACK/NACK feedback for each communication910 a, 910 b, 910 c) and/or aggregated decoding results 930 for eachcomponent carrier and/or each TRP. Alternatively, the network mayconfigure the UE to report an accumulation of the decoding results 920and/or aggregated decoding result 930 for all component carriers and/orall TRPs.

FIG. 10 illustrates a HARQ feedback history reporting scheme 1000according to some embodiments of the present disclosure. The scheme 1000may be employed by a BS such as the BSs 105, 304, 404, 600, 804, and 904and a UE such as the UEs 115, 302, 402, 500, 802, and/or 902 in anetwork such as the network 100. In particular, the UE may provide theBS with a HARQ feedback history on a per service basis. In FIG. 10, thex-axis represents time in some arbitrary units. The scheme 1000 may usea substantially similar transmission frame structure as shown in FIG. 2,and may use the same reference numerals as in FIG. 2 for simplicitysake. The scheme 1000 may use substantially similar mechanism for HARQcommunications as in the schemes 700, 800, and/or 900.

In the scheme 1000, a BS 1004 (e.g., the BSs 105, 304, 404, 600, 804,and/or 904) transmit a plurality of DL communications 1010 to a UE 1002(e.g., the UEs 115, 302, 402, 500, 802, and/or 902). The DLcommunications 1010 can include multiple traffic types associated withdifferent services. For example, the DL communications 1010 can includeone traffic type associated with an eMBB service (e.g., with a highthroughput requirement) and another traffic type associated with a URLLCservice (e.g., with a low latency requirement). The DL communication1010 for the eMBB service may be referred to as 1010 a (marked as E).The DL communication 1010 for the URLLC service may be referred to as1010 b (marked as U).

The UE 1002 may receive the DL communications 1010 from the BS 1004. TheUE 1002 may determine a decoding result 1020 for each received DLcommunication 1010 a and each received DL communication 1010 b. In anexample, the UE 1002 may transmit an individual feedback for eachreceived DL communication 1010 a and each received DL communication 1010b based on a corresponding decoding result 1020. The UE 1002 maytransmit an ACK (e.g., the ACK 340) for a successful decoding andtransmit a NACK (e.g., the NACK 342) for a failed decoding.

The UE 1002 may record all the decoding results 1020, for example, in amemory similar to the memory 504. For example, the UE 1002 may generatea record of the decoding, including in each entry, a decoding result1020 for a DL communication 1010 and a corresponding service or traffictype. As shown by the reference numeral 1050, the UE 1002 receives afirst DL communication for the eMBB service with a decoding success,receives a second DL communication for the URLLC service with a decodingsuccess, receives a third DL communication for the eMBB service with afailed decoding, and so on.

The BS 1004 may configure the UE 1002 to provide a HARQ feedback historyreport via a HARQ feedback history channel using similar mechanisms asin the schemes 700, 800, and 900. The UE may compute an aggregateddecoding result 1030 for the eMBB communications and an aggregateddecoding result 1030 for the URLLC communications in the record. Theaggregated decoding result 1030 can be based on a decoding success rateas shown in Equation (1) above. As shown, the aggregated decoding result1030 for the eMBB communications is about 75% and the aggregateddecoding result 1030 for the URLLC communications is about 100%. The BS1004 may configure the UE 1002 to provide the HARQ feedback historyreport on a per service basis.

In an example, the UE 1002 transmits a HARQ feedback history report 1040indicating the aggregated decoding result 1030 for the eMBBcommunications 1010 a and another HARQ feedback history report 1040indicating the aggregated decoding result 1030 for the URLLCcommunications 1010 b. In example, the UE 1002 transmits a single HARQfeedback history report 1040 indicating the aggregated decoding result1030 for the eMBB communications 1010 a and the aggregated decodingresult 1030 for the URLLC communications 1010 b. In an example, the UE1002 transmits a HARQ feedback history report 1040 indicating anaccumulation of the decoding results 1020 for the eMBB communications1010 a (e.g., including an ACK/NACK for each eMBB communication 1010 a)and another HARQ feedback history report 1040 indicating an accumulationof the decoding results 1020 for the URLLC communications 1010 b (e.g.,an ACK/NACK for each URLLC communication 1010 b). In another example,the UE 1002 transmits a single HARQ feedback history report 1040indicating the accumulated decoding results 1020 for the eMBBcommunications 1010 a and the accumulated decoding results 1020 for theURLLC communications 1010 b.

In some examples, the information associated with the accumulateddecoding results 1020 and/or the aggregated decoding results 1030,included in the HARQ feedback history report 1040 may includeinformation similar to that described above in FIG. 8.

In some examples, the plurality of BS 1004 may receive the HARQ feedbackhistory report 1040 and may use the information associated with theaccumulated decoding results 1020 and/or the aggregated decoding results1030 to jointly and/or individually improve outer-loop control and/ortracking, which may include performing power adjustments for theplurality of physical DL channels, inner-loop control adjustments forthe plurality of physical DL channels, downlink link adaptation for theplurality of physical DL channels, and/or the like.

In some instances, a HARQ feedback for the URLLC service can collidewith a HARQ feedback for the eMBB service. For example, the UE 1002 maybe required to transmit an individual feedback (e.g., an ACK 340 or aNACK 342) at the same time. The URLLC service has a more stringentlatency requirement than the eMBB service. Accordingly, the UE 1002 mayprioritize the transmission of the feedback for the URLLC service overthe feedback for the eMBB service. In other words, the UE 1002 may dropthe feedback for the eMBB service and transmit the feedback for theURLLC service. The dropping of the feedback for the eMBB service cancause unnecessary retransmission. For example, the UE 1002 decoded theeMBB communication successfully and the feedback is an ACK. Due to thedropped eMBB feedback transmission, the BS 1004 may determine that theeMBB communication failed and retransmit the eMBB communication. Withthe HARQ history feedback report from the UE 1002 (providing allfeedback records in the decoding results 820 for the eMBBcommunications), the BS 1004 may detect and recover the dropped eMBBfeedback(s). Referring to the reference numeral 1050, the UE 1002 caninclude an ACK for the first communication, a NACK for the thirdcommunication, an ACK for the fourth communication, and an ACK for theseventh communication in the report 1040. If the BS mis-detect the NACKfrom the third communication, the BS 1004 can detect the misdetectionbased on the report 1040 and update and/or correct the HARQ processingfor the third communication. Accordingly, the present disclosure canimprove eMBB efficiency.

FIG. 11 illustrates a HARQ feedback history reporting scheme 1100according to some embodiments of the present disclosure. The scheme 1100may be employed by a BS such as the BSs 105, 304, 404, 600, 804, 904,and/or 1004 and a UE such as the UEs 115, 302, 402, 500, 802, 902,and/or 1002 in a network such as the network 100. In particular, the UEmay provide the BS with a HARQ feedback history on a per HARQ processbasis. In FIG. 11, the x-axis represents time in some arbitrary units.The scheme 1100 may use a substantially similar transmission framestructure as shown in FIG. 2, and may use the same reference numerals asin FIG. 2 for simplicity sake. The scheme 1100 may use substantiallysimilar mechanism for HARQ communications as in the schemes 700, 800,900, and/or 1000.

In the scheme 1100, a BS 1104 (e.g., the BSs 105, 304, 404, 600, 804,904, and/or 1004) transmits a plurality of DL communications 1110 to aUE 1102 (e.g., the UEs 115, 302, 402, 500, 802, 902, and/or 1002). TheDL communications 1110 can be associated with multiple HARQ processes(e.g., the HARQ processes). For example, a first DL communication 1110may include a TB or DL data (e.g., the data blocks 330 and 332)associated with one HARQ process (e.g., H1 of FIG. 3) and a second DLcommunication 1110 may include a TB or DL data associated with anotherHARQ process (e.g., H2 of FIG. 3).

The UE 1102 may receive the DL communications 1110 from the BS 1102. TheUE 1102 may determine a decoding result for each received DLcommunication 1110. In an example, the UE 1102 may transmit anindividual feedback for each received DL communication 1110 based on acorresponding decoding result. The UE 1102 may transmit an ACK (e.g.,the ACK 340) for a successful decoding and transmit a NACK (e.g., theNACK 342) for a failed decoding.

The reference numeral 1150 illustrates the feedbacks transmitted by theUE 1102. An ACK (e.g., the ACK 340) is marked as A and a NACK (e.g., theNACK 342) is marked as N. As shown, for the HARQ process H1, the UE 1102transmits a NACK in slot S1 202, transmits an ACK in slot S7 202, andtransmits an ACK in slot S1 202. For the HARQ process H1, the UE 1102transmits a NACK in slot S3 202, transmits an ACK in slot S5 202, andtransmits a NACK in slot S9 202.

The BS 1104 may request for a HARQ feedback history report 1140 from theUE 1102 at slot S13 202. The UE 1102 may transmit the most recent orlatest feedback for each HARQ process to the BS 1102. As shown, the UE1102 may transmit an ACK for the HARQ process H1 (based on the ACK inthe slot S11 202) and a NACK for the HARQ process H2 (based on the NACKin the slot S9 202). In an example, the UE 1102 may maintain or trackthe most recent individual HARQ-ACK feedback for each HARQ process. Thereporting of the most recent HARQ-ACK feedback for a HARQ process can beuseful since if two HARQ ACK/NACKs (for two TBs) belong to the same HARQprocess, the UE 1102 may have flushed the HARQ buffer for earlier TB andmay not benefit from chase combining or incremental redundancy (IR)combining.

In an example, the BS 1104 may configure the UE 1102 to include the mostrecent HARQ feedback for all HARQ processes in the HARQ feedback historyreport 1140. In an example, the BS 1104 may configure the UE 1102 toinclude the most recent HARQ feedback for a subset of HARQ processes inthe HARQ feedback history report 1140. In an example, the UE 1102 isserved by multiple cells (e.g., the BSs 1104). In such an example, theUE 1102 may be configured to include the most recent HARQ feedback forall HARQ processes on one or multiple serving cells in the HARQ feedbackhistory report 1140

FIG. 12 illustrates a codebook configuration scheme 1200 for HARQfeedbacks according to some embodiments of the present disclosure. Thescheme 1200 may be employed by a BS such as the BSs 105, 304, 404, 600,804, 904, 1004, and/or 1104 and a UE such as the UEs 115, 302, 402, 500,802, 902, 1002, and/or 1102 in a network such as the network 100. Thescheme 1200 can be employed in conjunction with the schemes 700, 800,900, 1000, and 1100 described above. In particular, the BS may configurethe UE with multiple codebooks for HARQ feedback transmissions. FIG. 12illustrates two codebooks, a codebook A 1260 and a codebook B forpurposes of simplicity of discussion, though it will be recognized thatembodiments of the present disclosure may scale to many more codebooks(e.g., 3, 4, or more). In FIG. 12, the x-axis represents time in somearbitrary units.

In the scheme 1200, a BS 1204 (e.g., the BSs 105, 304, 404, 600, 804,904, 1004, and/or 1104) transmits DL communications 1210 (e.g., the datablocks 330 and 332, the DL communication 810, 910, 1010, and/or 1110) aUE 1202 (e.g., the UEs 115, 302, 402, 500, 802, 902, 1002, and/or 1102).The UE 1202 can transmit an individual feedback (e.g., the ACKs 340and/or the NACKs 342) for each DL communication 1210 using similarmechanisms described above in the schemes 700-1100. For example, the UEmay transmit an ACK (marked as A) in the slot S3 202 and the slot S11202. The UE may transmit a NACK (marked as N) in the slot S5 202. The UE1202 may transmit a HARQ feedback history report 1240 (e.g., the reports740, 840, 940, 1040, and/or 1140) for a period 1206. The HARQ feedbackhistory report 1240 may be transmitted in the slot S14 202. The slot 14202 where the HARQ feedback history report 1240 is transmitted and thereporting period 1206 can be configured by the BS 1204 in a substantialsimilar manner as described above in the schemes 700-1100.

The BS 1204 may configure the UE 1202 with a codebook A 1260 and acodebook B 1262 for the HARQ ACK/NACK and HARQ feedback history reporttransmissions. The codebook A 1260 can be used for transmittingindividual HARQ ACK/NACK feedbacks. The codebook B 1262 can be used fortransmitting a HARQ feedback history report 1240. Each individual HARQACK/NACK is typically a single bit feedback indicating an ACK or a NACK.However, the HARQ feedback history report 1240 may include multiplebits. The number of bits in the report 1240 may depend on whether thescheme 700, 800, 900, 1000, or 1100 is used and/or the specific HARQfeedback history configuration configured by the BS 1204.

In an example, when using the scheme 700, where a HARQ feedback historyreport is associated with a reporting period (e.g., the period 702) andincludes each individual HARQ ACK/NACK within the reporting period 1206,the number of bits in the HARQ feedback history report may varydepending on the reporting period 1206. In some examples, the BS 1204may configure the UE 1202 to report decoding results in groups oftransmission occasions or a subset of transmission occasions within thereporting period 1206. Accordingly, the size of the codebook B 1262 usedfor HARQ feedback history report transmission may vary depending on thereport configuration. As an example, when the report 1240 is configuredto include each individual HARQ feedback in a reporting period with tentransmission occasions (e.g., the transmission occasions 322), the sizeof the codebook B 1262 provide at least 10 bits of ACK/NACKcommunications. In general, the codebook A 1260 used for individual orinstantaneous HARQ ACK/NACKs may have a smaller codebook size than thecodebook B 1262. A particular HARQ ACK/NACK may be represented in thecodebook A 1260 and the codebook B 1262.

In an example, the configuration for the codebook B 1260 can be dynamic.For example, the BS 1204 may dynamically indicate, in a DCI message, aduration of ACK/NACK history for reporting. Alternatively oradditionally, the BS 1204 may indicate which of the transmissionoccasions (e.g., the transmission occasions 322) to include in thereporting. For example, for a reporting period with ten transmissionoccasions, the BS 1204 may request the UE 1202 to include the first,third, and eighth transmission occasions within the reporting periodusing a bitmap shown below:Reporting Bitmap=[1010000100].The selective reporting can be useful, for example, in selectingtransmission occasions associated with a particular traffic type orservice type, such as eMBB or URLLC. The BS 1204 can then resolve orrecover missed HARQ feedback transmissions for the eMBB or the URLLC dueto eMBB/URLLC collisions or any other type of transmission errors forthe particular service type.

In an example, the configuration for the codebook B 1260 can besemi-static. For example, the BS 1204 may semi-statically configure theUE 1202 with a duration for the reporting via an RRC configuration or agroup common DCI. The BS 1204 may configure the codebook B 1260 with acodebook size that is based on the time duration or the number ofpotential transmission occasions in the time duration.

In an example, the BS 1204 may indicate, in a DCI, the locations (orcodewords) within the codebook A 1260 for use with actual HARQ ACK/NACKfeedback back, where the remaining locations within the codebook A 1260can be used for NACK transmissions (e.g., to represent a DTX scenario).

In some examples, the BS 1204 may configure the UE 1202 to transmit theindividual HARQ ACK/NACKs and/or the HARQ feedback history report 1240using PUCCH resources. The BS 1204 may signal the PUCCH resource forindividual HARQ ACK/NACK transmission via a PDCCH DCI. The BS 1204 maysignal the PUCCH resource for HARQ feedback history report transmissionvia an RRC configuration.

In some embodiments, when a BS (e.g., BSs 105, 304, 404, 600, 804, 904,1004, 1104, and/or 1204) and a UE (e.g., UEs 115, 302, 402, 500, 802,902, 1002, 1102, and/or 1202) employ the schemes 700, 800, 900, 1000,1100, and/or 1200 for HARQ feedback history report communications, theUE may disable individual ACK/NACK feedback transmission (e.g., the ACKs340 and/or the NACKs 342). The UE may provide the BS with ACK/NACKfeedback information by transmitting a HARQ feedback history report(e.g., the HARQ feedback history reports 740, 840, 940, 1040, 1140,and/or 1240) at certain time intervals. In an example, the BS maydynamically configure the UE to enable or disable the individualACK/NACK feedback transmission (e.g., via an RRC configuration).

FIG. 13 is a signaling diagram illustrating a HARQ feedback historyreporting method 1300 according to some embodiments of the presentdisclosure. The method 1300 may be implemented between a BS (e.g., BSs105, 304, 404, 600, 804, 904, 1004, 1104, and/or 1204) and a UE (e.g.,UEs 115, 302, 402, 500, 802, 902, 1002, 1102, and/or 1202). The method1300 may employ similar mechanisms as in the schemes 700, 800, 900,1000, 1100, and/or 1200 described above with respect to FIGS. 7, 8, 9,10, 11, and/or 12, respectively. Steps of the method 1300 can beexecuted by computing devices (e.g., a processor, processing circuit,and/or other suitable component) of the BS and the UE. In an example,the BS may utilize one or more components, such as the processor 602,the memory 604, the HARQ module 608, the transceiver 610, the modem 612,and the one or more antennas 616, to execute the steps of method 1300.The UE may utilize one or more components, such as the processor 502,the memory 504, the HARQ module 508, the transceiver 510, the modem 512,and the one or more antennas 516, to execute the steps of method 1300.As illustrated, the method 1300 includes a number of enumerated steps,but embodiments of the method 1300 may include additional steps before,after, and in between the enumerated steps. In some embodiments, one ormore of the enumerated steps may be omitted or performed in a differentorder.

At step 1310, the BS transmits a feedback history configuration to theUE. The configuration may be a semi-static configuration for configuringand/or transmitting a HARQ feedback history report (e.g., the reports740, 840, 940, 1040, 1140, and/or 1240). The configuration can be an RRCconfiguration. The configuration may include a HARQ feedback historyreporting periodicity (e.g., the period 702 and 1206), a codebook (e.g.,the codebook B 1262) for transmitting the report. In some examples, theconfiguration may indicate which of the transmission occasions withinthe reporting period to be included in the report. In some examples, theconfiguration may request the report to be on a per component carrierbasis, a per TRP basis, a per traffic or service basis, and/or per HARQprocess basis. In some examples, the configuration may request thereport for a certain component carrier (e.g., the component carriers C1806 or C2 808), a certain TRP (e.g., the BS 904 a, 904 b, or 904 c), acertain traffic type or service (e.g., eMBB or URLLC), and/or a certainHARQ process (e.g., the HARQ process 312). In some examples, theconfiguration may request the report to indicate an accumulation ofdecoding results (e.g., the results 820, 920, and/or 1020) or aggregateddecoding result (e.g., the results 830, 930, and/or 1030) in variousforms, such as in percentage, fraction, an accumulation of a number ofACKs (e.g., by counting the number of ACKs), an accumulation of a numberof NACKs, and/or based on a certain threshold.

In an example, the configuration can indicate a resource fortransmitting the report. For example, the resource can be a resource ina PUCCH. Alternatively, the resource can be in a PUSCH channel. When theresource is in a PUSCH channel, the report can be piggyback with PUSCHdata or transmitted in a MAC CE.

At step 1320, the BS communicates HARQ communications with the UE. Forexample, the BS can transmit a plurality of DL communications (e.g., thedata blocks 330 and 332 and/or the DL communications 810, 910, 1010,1110, and/or 1210) to the UE and the UE can provide an individual HARQACK/NACK (e.g., the ACKs 340 and/or the NACKs 342) for each DLcommunication in a similar manner as described above in the schemes700-1100 described above.

At step 1330, the UE generates a record of feedback history. The UE mayperform the step 1330 can be in concurrent with the step 1320.

At step 1340, the UE transmits a HARQ feedback history report to the BSfrom the generated record according to the received configuration. In anexample, the UE may transmit the report periodically based on areporting periodicity in the configuration.

In some examples, the UE may skip a HARQ feedback history occasion. Inother words, the UE may not transmit a HARQ feedback history report fora particular reporting period. In an example, when the UE does notreceive any PDSCH transmission during the reporting period, the UE maynot transmit a HARQ feedback history report for the reporting period. Inan example, when the HARQ feedback history for a reporting periodincludes all NACKs, the UE may not transmit a HARQ feedback historyreport for the reporting period. In an example, when the UE determinesthat no individual ACK/NACK transmission is dropped (e.g., no collisionand no yielding to a higher priority traffic such as URLLC traffic), theUE may not transmit a HARQ feedback history report for the reportingperiod.

FIG. 14 is a signaling diagram illustrating a HARQ feedback historyreporting method 1400 according to some embodiments of the presentdisclosure. The method 1400 may be implemented between a BS (e.g., BSs105, 304, 404, 600, 804, 904, 1004, 1104, and/or 1204) and a UE (e.g.,UEs 115, 302, 402, 500, 802, 902, 1002, 1102, and/or 1202). The method1400 may employ similar mechanisms as in the schemes 700, 800, 900,1000, 1100, 1200, and/or 1300 described above with respect to FIGS. 7,8, 9, 10, 11, 12, and/or 13, respectively. Steps of the method 1400 canbe executed by computing devices (e.g., a processor, processing circuit,and/or other suitable component) of the BS and the UE. In an example,the BS may utilize one or more components, such as the processor 602,the memory 604, the HARQ module 608, the transceiver 610, the modem 612,and the one or more antennas 616, to execute the steps of method 1400.The UE may utilize one or more components, such as the processor 502,the memory 504, the HARQ module 508, the transceiver 510, the modem 512,and the one or more antennas 516, to execute the steps of method 1400.As illustrated, the method 1400 includes a number of enumerated steps,but embodiments of the method 1400 may include additional steps before,after, and in between the enumerated steps. In some embodiments, one ormore of the enumerated steps may be omitted or performed in a differentorder. The method 1400 may be substantially similar to the method 1300,but may use a dynamic trigger for HARQ feedback history reportinginstead of a semi-static configuration as in the method 1300.

At step 1410, the BS communicates HARQ communications with the UE. Forexample, the BS can transmit a plurality of DL communications (e.g., thedata blocks 330 and 332 and/or the DL communications 810, 910, 1010,1110, and/or 1210) to the UE and the UE can provide an individual HARQACK/NACK (e.g., the ACKs 340 and/or the NACKs 342) for each DLcommunication in a similar manner as described above in the schemes700-1100 described above.

At step 1420, the BS transmits a feedback history trigger to request aHARQ feedback history report (e.g., the reports 740, 840, 940, 1040,1140, and/or 1240) from the UE. The trigger is a dynamic trigger. Forexample, the BS may transmit the trigger in a slot (e.g., the slots 202)requesting a report for the past ten transmission occasions or since alast trigger and may request the report to be sent in the same slot orin a next slot. The trigger can be transmitted via a PDCCH DCI message.The trigger can be included in a DL scheduling grant or a UL schedulinggrant. When the trigger is included in a DL scheduling grant, thetrigger may indicate a PUCCH resource for transmitting the report. Whenthe trigger is included in a UL scheduling grant (e.g., indicating aPUSCH resource for PUSCH transmission), the report can be transmittedusing the PUSCH resource (e.g., piggyback on the PUSCH resource).

In some examples, the trigger can be transmitted in a group common DCI.The group common DCI may be configured for a group of UEs. In suchexamples, the UE may periodically monitor a group common DCI, forexample, based on a certain time duration associated with a reportingperiodicity. The inclusion of the trigger in a group common DCI canprovide several benefits. For example, the signaling group common DCIinstead of UE-specific DCI can reduce network signaling overhead.Additionally, the trigger may impact the existing scheduling DCI messagestructure.

The trigger can include a report configuration similar to the reportconfiguration described above in the method 1300. In an example, thetrigger can indicate a codebook (e.g., the codebook B 1262) for HARQfeedback history report transmission. With the dynamic trigger, the BShas the flexibility to select a different codebook for a certain HARQfeedback history report transmission.

FIG. 15 is a flow diagram of a communication method 1500 according tosome embodiments of the present disclosure. Steps of the method 1500 canbe executed by a computing device (e.g., a processor, processingcircuit, and/or other suitable component) of a wireless communicationdevice or other suitable means for performing the steps. For example, awireless communication device, such as the UE 115. UE 302, UE 402, UE500, UE 802, UE 902, UE 1002, UE 1102, UE 1202, may utilize one or morecomponents, such as the processor 502, the memory 504, the HARQ module508, the transceiver 510, the modem 512, and the one or more antennas516, to execute the steps of method 1500. The method 1500 may employsimilar mechanisms as in the schemes 700, 800, 900, 1000, 1100, and/or1200 described above with respect to FIGS. 7, 8, 9, 10, 11, and/or 12,respectively, and/or the methods 1300 and/or 1400 described above withrespect to FIGS. 13, and/or 14, respectively. As illustrated, the method1500 includes a number of enumerated steps, but embodiments of themethod 1500 include additional steps before, after, and in between theenumerated steps. In some embodiments, one or more of the enumeratedsteps may be omitted or performed in a different order.

At step 1510, the method 1500 includes monitoring, by a UE, for aplurality of data blocks (e.g., the data blocks 330 and 332 and/or theDL communications 810, 910, 1010, 1110, and/or 1210) during a pluralityof transmission occasions (e.g., the transmission occasions 322).

At step 1520, the method 1500 includes receiving, by the UE, one or moredata blocks of the plurality of data blocks, each of the one or moredata blocks received in one of the plurality transmission occasions.

At step 1530, the method 1500 includes transmitting, by the UE, anindividual feedback (e.g., ACK 340 or NACK 342) for each of the one ormore data blocks indicating whether the data block is receivedsuccessfully.

At step 1540, the method 1500 includes transmitting, by the UE, afeedback history report (e.g., the HARQ feedback history reports 740,840, 940, 1040, 1140, and/or 1240) for one or more transmissionoccasions of the plurality of transmission occasions.

In an embodiment, the UE generates a NACK for each transmission occasionof the plurality of transmission occasions when no data block isreceived for the transmission occasion (e.g., a DTX scenario). The UEgenerates a record (e.g., the record 710) of feedback history for a timeperiod (e.g., the time period 702) including the plurality oftransmission occasions. The record of feedback history may include theNACK and the individual feedbacks for the received data blocks. In someembodiments, the step 1530 may be optional. For example, the UE may beconfigured to disable individual feedback transmission. Each individualfeedback may include an ACK or a NACK. In an embodiment, the feedbackhistory report includes the record of feedback history for the timeperiod. In an embodiment, the UE receives a configuration indicatingwhich of the plurality transmission occasions to include in the feedbackhistory report, where the feedback history report is transmitted basedon the configuration. In an embodiment, the feedback history report isbased on at least one of an accumulation of a number of the ACKs in therecord of feedback history, an accumulation of a number of the NACKs inthe record of feedback history, or an aggregated result based on thenumber of the ACKs and the number of the NACKs. For example, thefeedback history report includes an aggregated decoding result (e.g.,the aggregated decoding results 830, 930, and/or 1030) for the pluralityof occasions.

In an embodiment, the UE monitors for the plurality of data blocks in aplurality of component carriers (e.g., the component carriers 806 and808) associated with the plurality of transmission occasions. In anembodiment, the UE receives a configuration for configuring the feedbackhistory report based on a first component carrier of the plurality ofcomponent carriers, where the feedback history report is transmittedbased on the configuration.

In an embodiment, the UE monitors for the plurality of data blocks froma plurality of (TRPs) (e.g., the BSs 904 a, 904 b, and 904 c) associatedwith the plurality of transmission occasions. In an embodiment, the UEreceives a configuration for configuring the feedback history reportbased on a first TRP of the plurality of TRPs, where the feedbackhistory report is transmitted based on the configuration.

In an embodiment, the UE monitors the plurality of data blocks duringthe plurality of transmission occasions associated with a plurality ofservices. In an embodiment, the plurality of services includes a URLLCservice and an eMBB service. In an embodiment, the UE receives aconfiguration for configuring the feedback history report based on afirst service of the plurality of services, where the feedback historyreport is transmitted based on the configuration.

In an embodiment, the UE receives a first data block of the one or moredata blocks, the first data block associated with a first HARQ process(e.g., the HARQ processes 312). The UE receives a second data block ofthe one or more data blocks, the first data block associated with asecond HARQ process different from the first HARQ process. The UEincludes, in the feedback history report, first feedback historyinformation for the first HARQ process and second feedback historyinformation for the second HARQ process.

In an embodiment, the individual feedback is transmitted based on afirst codebook (e.g., the codebook A 1260) and the feedback historyreport is transmitted based on a second codebook (e.g., the codebook B1262) different from the first codebook.

In an embodiment, the UE receives at least one of a RRC configurationindicating a periodicity for the feedback history report or a DCImessage requesting for the feedback history report. In an embodiment,the UE receives a RRC configuration indicating a PUCCH resource for theUE to transmit the feedback history report (e.g., via a MAC CE) or aPUSCH resource for the UE to transmit the feedback history report (e.g.,via piggyback with PUSCH data). In an embodiment, the UE receives a DCImessage indicating a PUCCH resource for the UE to transmit the feedbackhistory report (e.g., via a MAC CE) or a PUSCH resource for the UE totransmit the feedback history report (e.g., via piggyback with PUSCHdata).

In an embodiment, the one or more data blocks are associated with atleast one a PDSCH or a PUCCH.

FIG. 16 is a flow diagram of a communication method 1600 according tosome embodiments of the present disclosure. Steps of the method 1600 canbe executed by a computing device (e.g., a processor, processingcircuit, and/or other suitable component) of a wireless communicationdevice or other suitable means for performing the steps. For example, awireless communication device, such as the BS 105, BS 304, BS 404, BS600, BS 804, BS 904, BS 1004, BS 1104, and/or BS 1204, may utilize oneor more components, such as the processor 602, the memory 604, the HARQmodule 608, the transceiver 610, the modem 612, and the one or moreantennas 616, to execute the steps of method 1600. The method 1600 mayemploy similar mechanisms as in the schemes 700, 800, 900, 1000, 1100,and/or 1200 described above with respect to FIGS. 7, 8, 9, 10, 11,and/or 12, respectively, and/or the methods 1300 and/or 1400 describedabove with respect to FIGS. 13, and/or 14, respectively. As illustrated,the method 1600 includes a number of enumerated steps, but embodimentsof the method 1600 include additional steps before, after, and inbetween the enumerated steps. In some embodiments, one or more of theenumerated steps may be omitted or performed in a different order.

At step 1610, the method 1600 includes transmitting, by the BS to a UE(e.g., the UEs 115, 302, 402, 500, 802, 902, 1002, 1102, and/or 1202), aplurality of data blocks (e.g., the data blocks 330 and 332 and/or theDL communications 810, 910, 1010, 1110, and/or 1210) during a pluralityof transmission occasions (e.g., the transmission occasions 322).

At step 1620, the method 1600 includes receiving, by the BS from the UE,an individual feedback (e.g., ACK 340 or NACK 342) for at least a firstdata block of the plurality of data blocks, the individual feedbackindicating whether the first data block is received successfully.

At step 1630, the method 1600 includes receiving, by the BS from the UE,a feedback history report (e.g., the HARQ feedback history reports 740,840, 940, 1040, 1140, and/or 1240) for one or more transmissionoccasions of the plurality of transmission occasions.

In an embodiment, the BS transmits, to the UE, a configurationindicating a periodicity (e.g., the time period 702 and 1206) for thefeedback history report. The received feedback history includes a record(e.g., the record 710) of feedback history for a time duration that isconfigured based on the periodicity, the time duration including theplurality of transmission occasions.

In an embodiment, the BS transmits a configuration indicating which ofthe plurality of transmission occasions to include in the feedbackhistory report.

In an embodiment, the BS transmits each of the plurality of data blocksin one of a plurality of component carriers (e.g., the componentcarriers 806 and 808). The BS transmits, to the UE, a configuration forconfiguring the feedback history report based on a first componentcarrier of the plurality of component carriers.

In an embodiment, the BS transmits each of the plurality of data blocksvia one of a plurality of TRPs (e.g., the BSs 904 a, 904 b, and 904 c)associated with the BS. The BS transmits, to the UE, a configuration forconfiguring the feedback history report based on a first TRP of theplurality of TRPs.

In an embodiment, the BS transmits each of the plurality of data blocksassociated with one of a plurality of services (e.g., URLLC or eMBB).The BS transmits, to the UE a configuration based on a first service ofthe plurality of services for the feedback history report.

In an embodiment, the BS transmits each of the plurality of data blocksassociated with one of a plurality of HARQ processes (e.g., the HARQprocesses 312). The BS transmits, to the UE, a configuration forconfiguring the feedback history report based on a first HARQ process ofthe plurality of HARQ processes.

In an embodiment, the BS transmits at least one of a RRC configurationmessage indicating a periodicity for the feedback history report or aDCI message requesting for the feedback history report. In anembodiment, the BS transmits a RRC configuration message indicating aPUCCH resource for the UE to transmit the feedback history report (e.g.,via a MAC CE) or a PUSCH resource for the UE to transmit the feedbackhistory report (e.g., via piggyback with PUSCH data). In an embodiment,the BS transmits a DCI message indicating a PUCCH resource for the UE totransmit the feedback history report (e.g., via a MAC CE) or a PUSCHresource for the UE to transmit the feedback history report (e.g., viapiggyback with PUSCH data). In an embodiment, the BS transmits a RRCconfiguration indicating a first codebook for the individual feedbackand a second codebook for the feedback history report, the firstcodebook being different from the second codebook.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of [at least one of A, B, or C]means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

As those of some skill in this art will by now appreciate and dependingon the particular application at hand, many modifications, substitutionsand variations can be made in and to the materials, apparatus,configurations and methods of use of the devices of the presentdisclosure without departing from the spirit and scope thereof. In lightof this, the scope of the present disclosure should not be limited tothat of the particular embodiments illustrated and described herein, asthey are merely by way of some examples thereof, but rather, should befully commensurate with that of the claims appended hereafter and theirfunctional equivalents.

What is claimed is:
 1. A method of wireless communication, comprising:receiving, by a user equipment (UE), one or more data blocks, each ofthe one or more data blocks received in one of a plurality oftransmission occasions; transmitting, by the UE, an individual feedbackfor each of the one or more data blocks indicating whether the datablock is received successfully; and transmitting, by the UE, a feedbackhistory report for one or more transmission occasions of the pluralityof transmission occasions, wherein the feedback history report is basedon the individual feedback for each of the one or more data blocksreceived in the one of the plurality of transmission occasions.
 2. Themethod of claim 1, further comprising: generating, by the UE, anegative-acknowledgement (NACK) for each transmission occasion of theplurality of transmission occasions when no data block is received forthe transmission occasion; and generating, by the UE, a record offeedback history for a time period including the plurality oftransmission occasions, the record of feedback history including theNACK and the individual feedback, the individual feedback including anacknowledgement (ACK) or a NACK.
 3. The method of claim 1, wherein thetransmitting the feedback history report includes: transmitting, by theUE, the feedback history report including a record of feedback historyfor a time period.
 4. The method of claim 1, further comprising:receiving, by the UE, a configuration indicating which of the pluralityof transmission occasions to include in the feedback history report,wherein the transmitting the feedback history report is further based onthe configuration.
 5. The method of claim 1, wherein the transmittingthe feedback history report includes: transmitting, by the UE, thefeedback history report based on at least one of an accumulation of anumber of acknowledgements (ACKs) in a record of feedback history, anaccumulation of a number of negative-acknowledgements (NACKs) in therecord of feedback history, or an aggregated result based on the numberof the ACKs and the number of the NACKs.
 6. The method of claim 1,wherein the transmitting the feedback history report includes:transmitting, by the UE, the feedback history report including a recordof feedback history for at least one of: a first component carrier of aplurality of component carriers associated with the plurality oftransmission occasions; a first transmission reception point (TRP) of aplurality of TRPs associated with the plurality of transmissionoccasions; or a first service of a plurality of services associated withthe plurality of transmission occasions.
 7. The method of claim 6,further comprising: receiving, by the UE, a configuration forconfiguring the feedback history report based on the at least one of thefirst component carrier, the first TRP, or the first service, whereinthe transmitting the feedback history report is further based on theconfiguration.
 8. The method of claim 6, wherein the transmittingincludes: transmitting, by the UE, the feedback history report includingthe record of feedback history for the first service of the plurality ofservices, the plurality of services including an ultra-reliablelow-latency communications (URLLC) service and an enhanced mobilebroadband (eMBB) service.
 9. The method of claim 1, wherein: thereceiving includes: receiving, by the UE, a first data block of the oneor more data blocks, the first data block associated with a first hybridautomatic repeat request (HARQ) process; and receiving, by the UE, asecond data block of the one or more data blocks, the first data blockassociated with a second HARQ process different from the first HARQprocess; and the transmitting the feedback history report includes:transmitting, by the UE, the feedback history report including firstfeedback history information for the first HARQ process and secondfeedback history information for the second HARQ process.
 10. The methodof claim 1, wherein: the transmitting the individual feedback is basedon a first codebook; and the transmitting the feedback history report isbased on a second codebook different from the first codebook.
 11. Themethod of claim 1, further comprising: receiving, by the UE, at leastone of a radio resource control (RRC) configuration indicating aperiodicity for the feedback history report or a downlink controlinformation (DCI) message requesting for the feedback history report.12. The method of claim 11, wherein the receiving includes: receiving,by the UE, at least one of: the RRC configuration indicating a physicaluplink control channel (PUCCH) resource for the feedback history reportor a physical uplink shared channel (PUSCH) resource for the feedbackhistory report; or the DCI message indicating a PUCCH resource for thefeedback history report or a PUSCH resource for the feedback historyreport.
 13. The method of claim 1, wherein the one or more data blocksare associated with at least one a physical downlink shared channel(PDSCH) or a physical downlink control channel (PDCCH).
 14. A method ofwireless communication, comprising: transmitting, by a base station (BS)to a user equipment (UE), a plurality of data blocks during a pluralityof transmission occasions; receiving, by the BS from the UE, anindividual feedback for at least a first data block of the plurality ofdata blocks, the individual feedback indicating whether the first datablock is received successfully; and receiving, by the BS from the UE, afeedback history report for one or more transmission occasions of theplurality of transmission occasions, wherein the feedback history reportis based on the individual feedback for at least the first data block.15. The method of claim 14, further comprising: transmitting, by the BSto the UE, a configuration indicating a periodicity for the feedbackhistory report, wherein the receiving the feedback history reportincludes: receiving, by the BS from the UE, a record of feedback historyfor a time duration that is configured based on the periodicity, thetime duration including the plurality of transmission occasions.
 16. Themethod of claim 14, further comprising: transmitting, by the BS, aconfiguration indicating which of the plurality of transmissionoccasions to include in the feedback history report.
 17. The method ofclaim 14, further comprising: transmitting, by the BS to the UE, aconfiguration for configuring the feedback history report based on atleast one of: a first component carrier of a plurality of componentcarriers associated with the plurality of transmission occasions; afirst transmission reception point (TRP) of a plurality of TRPsassociated with the plurality of transmission occasions; or a firstservice of a plurality of services associated with the plurality oftransmission occasions.
 18. The method of claim 17, wherein thetransmitting the configuration includes: transmitting, by the BS to theUE, the configuration for configuring the feedback history report basedon the first service of the plurality of services, the plurality ofservices including an ultra-reliable low-latency communications (URLLC)service and an enhanced mobile broadband (eMBB) service.
 19. The methodof claim 14, wherein: the transmitting includes: transmitting, by theBS, each of the plurality of data blocks associated with one of aplurality of hybrid automatic repeat request (HARQ) processes; and themethod further comprises: transmitting, by the BS to the UE, aconfiguration for configuring the feedback history report based on afirst HARQ process of the plurality of HARQ processes.
 20. The method ofclaim 14, further comprising: transmitting, by the BS, at least one of:a radio resource control (RRC) configuration message indicating at leastone of a periodicity for the feedback history report, a physical uplinkcontrol channel (PUCCH) resource for the feedback history report, aphysical uplink shared channel (PUSCH) resource for the feedback historyreport, a codebook for the individual feedback, or a codebook for thefeedback history report; or a downlink control information (DCI) messagerequesting for the feedback history report, the DCI message indicatingat least one of a PUCCH resource for the feedback history report, aPUSCH resource for the feedback history report, a codebook for theindividual feedback, or a codebook for the feedback history report. 21.A user equipment (UE) comprising: a transceiver configured to: receiveone or more data blocks, each of the one or more data blocks received inone of a plurality of transmission occasions; transmit an individualfeedback for each of the one or more data blocks indicating whether thedata block is received successfully; and transmit a feedback historyreport for one or more transmission occasions of the plurality oftransmission occasions, wherein the feedback history report is based onthe individual feedback for each of the one or more data blocks receivedin the one of the plurality of transmission occasions.
 22. The UE ofclaim 21, further comprising: a processor is configured to: generate anegative-acknowledgement (NACK) for each transmission occasion of theplurality of transmission occasions when no data block is received forthe transmission occasion; and generate a record of feedback history fora time period including the plurality of transmission occasions, therecord of feedback history including the NACK and the individualfeedback, the individual feedback including an acknowledgement (ACK) ora NACK, and wherein the feedback history report includes the record offeedback history.
 23. The UE of claim 21, wherein the transceiverconfigured to transmit the feedback history report is further configuredto: transmit the feedback history report including a record of feedbackhistory for a time period.
 24. The UE of claim 21, wherein thetransceiver configured to transmit the feedback history report isfurther configured to: transmit the feedback history report including arecord of feedback history for at least one of: a first componentcarrier of a plurality of component carriers associated with theplurality of transmission occasions; a first transmission receptionpoint (TRP) of a plurality of TRPs associated with the plurality oftransmission occasions; a first service of a plurality of servicesassociated with the plurality of transmission occasions; or a firsthybrid automatic repeat request (HARQ) process of a plurality of HARQprocesses associated with the plurality of transmission occasions. 25.The UE of claim 24, wherein the transceiver is further configured to:receive a configuration for configuring the feedback history reportbased on the at least one of the first component carrier, the first TRP,the first service, or the first HARQ process, and wherein the feedbackhistory report is transmitted based on the configuration.
 26. The UE ofclaim 21, wherein the transceiver is further configured to: receive atleast one of: a radio resource control (RRC) configuration indicating atleast one of a periodicity for the feedback history report, a physicaluplink control channel (PUCCH) resource for the feedback history report,a physical uplink shared channel (PUSCH) resource for the feedbackhistory report, a codebook for the individual feedback, or a codebookfor the feedback history report; or a downlink control information (DCI)message requesting for the feedback history report, the DCI messageindicating at least one of a PUCCH resource for the feedback historyreport, a PUSCH resource for the feedback history report, a codebook forthe individual feedback, or a codebook for the feedback history report.27. A base station (BS) comprising: a transceiver configured to:transmit, to a user equipment (UE), a plurality of data blocks during aplurality of transmission occasions; receive, from the UE, an individualfeedback for at least a first data block of the plurality of datablocks, the individual feedback indicating whether the first data blockis received successfully; and receive, from the UE, a feedback historyreport for one or more transmission occasions of the plurality oftransmission occasions, wherein the feedback history report is based onthe individual feedback for at least the first data block.
 28. The BS ofclaim 27, wherein the transceiver configured to receive the feedbackhistory report is further configured to: receive the feedback historyreport including a record of feedback history for a time period.
 29. TheBS of claim 27, wherein the transceiver is further configured to:transmit, to the UE, a configuration for configuring the feedbackhistory report based on at least one of: a first component carrier of aplurality of component carriers associated with the plurality oftransmission occasions; a first transmission reception point (TRP) of aplurality of TRPs associated with the plurality of transmissionoccasions; a first service of a plurality of services associated withthe plurality of transmission occasions; or a first hybrid automaticrepeat request (HARQ) process of a plurality of HARQ processesassociated with the plurality of transmission occasions.
 30. The BS ofclaim 27, wherein the transceiver is further configured to: transmit atleast one of: a radio resource control (RRC) configuration indicating atleast one of a periodicity for the feedback history report, a physicaluplink control channel (PUCCH) resource for the feedback history report,a physical uplink shared channel (PUSCH) resource for the feedbackhistory report, a codebook for the individual feedback, or a codebookfor the feedback history report; or a downlink control information (DCI)message requesting for the feedback history report, the DCI messageindicating at least one of a PUCCH resource for the feedback historyreport, a PUSCH resource for the feedback history report, a codebook forthe individual feedback, or a codebook for the feedback history report.